package proto.security.authn

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message Authentication

authn.proto:9

Configuration of how users authenticate against Spinnaker.

Used in: Security

message Basic

authn.proto:308

Configuration for basic username/password authentication

Used in: config.SpringSecurity, Authentication

message Iap

authn.proto:289

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: config.Gate.GoogleConfig, Authentication

message Ldap

authn.proto:225

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: config.Gate, Authentication

message OAuth2

authn.proto:33

Configuration for authentication via OAuth 2.0.

Used in: config.SpringSecurity, Authentication

message OAuth2Client

authn.proto:54

Configuration for an OAuth 2.0 client.

Used in: OAuth2

enum OAuth2Client.AuthenticationScheme

authn.proto:84

Methods to transmit authentication tokens to an OAuth 2.0 provider.

Used in: OAuth2Client

message OAuth2Resource

authn.proto:103

Configuration for OAuth 2.0 resources.

Used in: OAuth2

message OAuth2UserInfoMapping

authn.proto:111

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: OAuth2

message Saml

authn.proto:132

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: config.Gate, Authentication

enum Saml.SignatureDigest

authn.proto:195

Digest algorithms to sign SAML messages.

Used in: Saml

message Saml.UserAttributes

authn.proto:174

Configuration for fields returned from your SAML provider.

Used in: Saml

message UsernamePassword

authn.proto:317

Configuration for a username/password combination.

Used in: Basic

message X509

authn.proto:269

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: config.Gate, Authentication