Get desktop application:
View/edit binary Protocol Buffers messages
Configuration of how users authenticate against Spinnaker.
Used in:
Whether to enabled authentication.
OAuth 2.0 configuration.
SAML configuration.
LDAP configuration.
X509 configuration.
Google Cloud Identity-Aware Proxy configuration.
Basic username/password authentication.
Configuration for basic username/password authentication
Used in: ,
Whether the authentication method is enabled.
The username and password used to log in via basic authentication.
Configuration for authentication via Google Cloud Identity-Aware Proxy. Google Cloud Identity-Aware Proxy (IAP) is an authentication model that utilizes Google OAuth 2.0 and an authorization service to provide access control for users of GCP. After a user has been authenticated and authorized by IAP's service, a JWT token is passed along which Spinnaker uses to check for authenticity and to get the user email from the payload and sign the user in. To configure IAP, set the audience field retrieved from the IAP console.
Used in: ,
Whether the authentication method is enabled.
The HTTP request header that contains the JWT token.
The Issuer from the ID token payload.
The Audience from the ID token payload. You can retrieve this field from the IAP console: https://cloud.google.com/iap/docs/signed-headers-howto#verify_the_id_token_header.
The URL containing the Cloud IAP public keys in JWK format.
Configuration for authentication via LDAP. Lightweight Directory Access Protocol (LDAP) is a standard way many organizations maintain user credentials and group memberships. Spinnaker uses the standard 'bind' approach for user authentication. This is a fancy way of saying that Gate uses your username and password to login to the LDAP server, and if the connection is successful, you're considered authenticated.
Used in: ,
Whether the authentication method is enabled.
ldap:// or ldaps:// url of the LDAP server.
The pattern for finding a user's DN using simple pattern matching. For example, if your LDAP server has the URL ldap://mysite.com/dc=spinnaker,dc=org, and you have the pattern 'uid={0},ou=members', 'me' will map to a DN uid=me,ou=members,dc=spinnaker,dc=org. If no match is found, will try to find the user using user-search-filter, if set.
The part of the directory tree under which user searches should be performed. If user-search-base isn't supplied, the search will be performed from the root.
The filter to use when searching for a user's DN. Will search either from user-search-base (if specified) or root for entires matching the filter, then attempt to bind as that user with the login password. For example, the filter 'uid={0}' would apply to any user where uid matched the user's login name. If -user-dn-pattern is also specified, will attempt to find a match using the specified pattern first, before searching with the specified search filter if no match is found from the pattern.
An LDAP manager user is required for binding to the LDAP server for the user authentication process. This property refers to the DN of that entry. I.e. this is not the user which will be authenticated when logging into DHIS2, rather the user which binds to the LDAP server in order to do the authentication.
The password for the LDAP manager user.
The part of the directory tree under which group searches should be performed.
Configuration for authentication via OAuth 2.0.
Used in: ,
Whether the authentication method is enabled.
Configuration for your OAuth 2.0 client.
The map of requirements the userInfo request must have. This is used to restrict user login to specific domains or having a specific attribute.
Configuration for OAuth 2.0 resources.
Mapping of user attributes to fields returned by your OAuth 2.0 provider. This field controls how the fields returned from the OAuth 2.0 provider's user info endpoint are translated into a Spinnaker user.
Configuration for an OAuth 2.0 client.
Used in:
The OAuth client ID you have configured with your OAuth 2.0 provider.
The OAuth client secret you have configured with your OAuth provider.
The access token uri for your OAuth provider.
The user authorization uri for your OAuth 2.0 provider.
The method used to transmit authentication credentials to your OAuth 2.0 provider.
The scope to request when obtaining an access token from your OAuth 2.0 provider.
The externally accessible URL for Gate. For use with load balancers that do any kind of address manipulation for Gate traffic, such as an SSL terminating load balancer.
Whether the current URI in the request should be preferred over the pre-established redirect URI.
Methods to transmit authentication tokens to an OAuth 2.0 provider.
Used in:
Unspecified. Do not directly use, instead omit the field.
Token is sent in the request header.
Token is sent as a query parameter.
Token is sent in the form body.
Token is not sent at all.
Configuration for OAuth 2.0 resources.
Used in:
The user info URI for your OAuth 2.0 provider.
Mapping of user attributes to fields returned by an OAuth 2.0 provider. This field controls how the fields returned from the OAuth 2.0 provider's user info endpoint are translated into a Spinnaker user.
Used in:
Email.
First name.
Last name.
Username.
Configuration for authentication via SAML. SAML authenticates users by passing cryptographically signed XML documents between the Gate server and an identity provider. Gate's key is stored and accessed via the -keystore parameters, while the identity provider's keys are included in the metadata.xml. Finally, the identity provider must redirect the control flow (through the user's browser) back to Gate by way of the -serviceAddressUrl. This is likely the address of Gate's load balancer.
Used in: ,
Whether the authentication method is enabled.
The path to a local file containing identity provider's metadata XML file; can be either a local file or a URI.
The identity of the Spinnaker application registered with the SAML provider.
Path to the keystore that contains this server's private key. This key is used to cryptographically sign SAML AuthNRequest objects.
The password used to access the file specified in -keystore.
The name of the alias under which this server's private key is stored in the -keystore file.
The host name of the gate server as accessible by the SAML identity provider. If deployed behind a load balancer, this would be the load balancer's address. (Ex: gate.org.com:8084)
The base path on the gate server to which redirects will be sent. Defaults to '/' if absent.
The protocol to use to when redirecting back to the Gate server. Defaults to 'https' if absent.
Configuration for fields returned from your SAML provider.
Digest algorithm to sign SAML messages (optional).
Digest algorithms to sign SAML messages.
Used in:
Unspecified. Do not directly use, instead omit the field.
Digest algorithm SHA1 (default).
Digest algorithm SHA256.
Digest algorithm SHA384.
Digest algorithm SHA512.
Digest algorithm RIPEMD160.
Digest algorithm MD5 (not recommended).
Configuration for fields returned from your SAML provider.
Used in:
First name.
Last name.
Roles.
Roles delimiter.
Username.
Email.
Configuration for a username/password combination.
Used in:
Username.
Password.
Configuration for authentication via X509 certificates. X509 authenticates users via client certificate and a corresponding private key. These certificates optionally provide authorization information via custom OIDs with corresponding group information for the user. This can be configured via -roleOid.
Used in: ,
Whether the authentication method is enabled.
The OID that encodes roles that the user specified in the x509 certificate belongs to.
The regex used to parse the subject principal name embedded in the x509 certificate if necessary.