The authentication scheme used by the REST Consumer to login to the REST host. Changes to this attribute are synchronized to HA mates and replication sites via config-sync. The default value is "none". The allowed values and their meaning are:

"none" - Login with no authentication. This may be useful for anonymous connections or when a REST Consumer does not require authentication.
"http-basic" - Login with a username and optional password according to HTTP Basic authentication as per RFC2616.
"client-certificate" - Login with a client TLS certificate as per RFC5246. Client certificate authentication is only available on TLS connections.
"http-header" - Login with a specified HTTP header.
"oauth-client" - Login with OAuth 2.0 client credentials.
"oauth-jwt" - Login with OAuth (RFC 7523 JWT Profile).
"transparent" - Login using the Authorization header from the message properties, if present. Transparent authentication passes along existing Authorization header metadata instead of discarding it. Note that if the message is coming from a REST producer, the REST service must be configured to forward the Authorization header.
"aws" - Login using AWS Signature Version 4 authentication (AWS4-HMAC-SHA256).

Enumeration Members

AWS: "aws"
CLIENT_CERTIFICATE: "client-certificate"
HTTP_BASIC: "http-basic"
HTTP_HEADER: "http-header"
NONE: "none"
OAUTH_CLIENT: "oauth-client"
OAUTH_JWT: "oauth-jwt"
TRANSPARENT: "transparent"