Bases: keystoneauth1.identity.v3.base.BaseAuth
Identity V3 Authentication Plugin.
Parameters: |
|
---|
Bases: object
One part of a V3 Authentication strategy.
V3 Tokens allow multiple methods to be presented when authentication against the server. Each one of these methods is implemented by an AuthMethod.
Note: When implementing an AuthMethod use the method_parameters and do not use positional arguments. Otherwise they can’t be picked up by the factory method and don’t work as well with AuthConstructors.
Return the authentication section of an auth plugin.
Parameters: |
|
---|---|
Returns: | The identifier of this plugin and a dict of authentication data for the auth type. |
Return type: | tuple(string, dict) |
Get the elements for this auth method that make it unique.
These elements will be used as part of the keystoneauth1.plugin.BaseIdentityPlugin.get_cache_id() to allow caching of the auth plugin.
Plugins should override this if they want to allow caching of their state.
To avoid collision or overrides the keys of the returned dictionary should be prefixed with the plugin identifier. For example the password plugin returns its username value as ‘password_username’.
Bases: keystoneauth1.identity.v3.base.Auth
Abstract base class for creating an Auth Plugin.
The Auth Plugin created contains only one authentication method. This is generally the required usage.
An AuthConstructor creates an AuthMethod based on the method’s arguments and the auth_method_class defined by the plugin. It then creates the auth plugin with only that authentication method.
Bases: keystoneauth1.identity.base.BaseIdentityPlugin
Identity V3 Authentication Plugin.
Parameters: |
|
---|
Does the plugin have parameters that will create a scoped token
The full URL where we will send authentication data.
Bases: keystoneauth1.identity.v3.federation._Rescoped
Plugin to execute the Keystone to Keyestone authentication flow.
In this plugin, an ECP wrapped SAML assertion provided by a keystone Identity Provider (IdP) is used to request an OpenStack unscoped token from a keystone Service Provider (SP).
Parameters: |
|
---|
Path where the ECP wrapped SAML assertion should be presented to the Keystone Service Provider.
Bases: keystoneauth1.identity.v3.oidc._OidcBase
Implementation for OpenID Connect Authorization Code
Authenticate with OpenID Connect and get back claims.
This is a multi-step process. First an access token must be retrieved, to do this, an authorization code and redirect URL must be given.
Secondly, we then exchange the access token upon accessing the protected Keystone endpoint (federated auth URL). This will trigger the OpenID Connect Provider to perform a user introspection and retrieve information (specified in the scope) about the user in the form of an OpenID Connect Claim. These claims will be sent to Keystone in the form of environment variables.
Parameters: | session (keystoneauth1.session.Session) – a session object to send out HTTP requests. |
---|---|
Returns: | a token data representation |
Return type: | keystoneauth1.access.AccessInfoV3 |
Bases: keystoneauth1.identity.v3.oidc._OidcBase
Implementation for OpenID Connect Resource Owner Password Credential
Authenticate with OpenID Connect and get back claims.
This is a multi-step process. First an access token must be retrieved, to do this, the username and password, the OpenID Connect client ID and secret, and the access token endpoint must be known.
Secondly, we then exchange the access token upon accessing the protected Keystone endpoint (federated auth URL). This will trigger the OpenID Connect Provider to perform a user introspection and retrieve information (specified in the scope) about the user in the form of an OpenID Connect Claim. These claims will be sent to Keystone in the form of environment variables.
Parameters: | session (keystoneauth1.session.Session) – a session object to send out HTTP requests. |
---|---|
Returns: | a token data representation |
Return type: | keystoneauth1.access.AccessInfoV3 |
Bases: keystoneauth1.identity.v3.base.AuthMethod
Construct a User/Password based authentication method.
Parameters: |
---|
Bases: keystoneauth1.identity.v3.base.AuthConstructor
A plugin for authenticating with a username and password.
Parameters: |
|
---|
Bases: keystoneauth1.identity.v3.base.AuthMethod
Construct an Auth plugin to fetch a token from a token.
Parameters: | token (string) – Token for authentication. |
---|
Bases: keystoneauth1.identity.v3.base.AuthConstructor
A plugin for authenticating with an existing Token.
Parameters: |
|
---|
Bases: keystoneauth1.identity.v3.base.BaseAuth
Identity V3 Authentication Plugin.
Parameters: |
|
---|
Bases: keystoneauth1.identity.v3.base.Auth
Abstract base class for creating an Auth Plugin.
The Auth Plugin created contains only one authentication method. This is generally the required usage.
An AuthConstructor creates an AuthMethod based on the method’s arguments and the auth_method_class defined by the plugin. It then creates the auth plugin with only that authentication method.
Bases: object
One part of a V3 Authentication strategy.
V3 Tokens allow multiple methods to be presented when authentication against the server. Each one of these methods is implemented by an AuthMethod.
Note: When implementing an AuthMethod use the method_parameters and do not use positional arguments. Otherwise they can’t be picked up by the factory method and don’t work as well with AuthConstructors.
Return the authentication section of an auth plugin.
Parameters: |
|
---|---|
Returns: | The identifier of this plugin and a dict of authentication data for the auth type. |
Return type: | tuple(string, dict) |
Get the elements for this auth method that make it unique.
These elements will be used as part of the keystoneauth1.plugin.BaseIdentityPlugin.get_cache_id() to allow caching of the auth plugin.
Plugins should override this if they want to allow caching of their state.
To avoid collision or overrides the keys of the returned dictionary should be prefixed with the plugin identifier. For example the password plugin returns its username value as ‘password_username’.
Bases: keystoneauth1.identity.base.BaseIdentityPlugin
Identity V3 Authentication Plugin.
Parameters: |
|
---|
Does the plugin have parameters that will create a scoped token
The full URL where we will send authentication data.
Bases: keystoneauth1.identity.v3.federation._Rescoped
Full URL where authorization data is sent.
Bases: keystoneauth1.identity.v3.federation._Rescoped
Plugin to execute the Keystone to Keyestone authentication flow.
In this plugin, an ECP wrapped SAML assertion provided by a keystone Identity Provider (IdP) is used to request an OpenStack unscoped token from a keystone Service Provider (SP).
Parameters: |
|
---|
Bases: keystoneauth1.identity.v3.base.AuthConstructor
A plugin for authenticating with a username and password.
Parameters: |
|
---|
Bases: keystoneauth1.identity.v3.base.AuthMethod
Construct a User/Password based authentication method.
Parameters: |
---|
Bases: keystoneauth1.identity.v3.base.AuthConstructor
A plugin for authenticating with an existing Token.
Parameters: |
|
---|
Bases: keystoneauth1.identity.v3.oidc._OidcBase
Implementation for OpenID Connect Resource Owner Password Credential
Authenticate with OpenID Connect and get back claims.
This is a multi-step process. First an access token must be retrieved, to do this, the username and password, the OpenID Connect client ID and secret, and the access token endpoint must be known.
Secondly, we then exchange the access token upon accessing the protected Keystone endpoint (federated auth URL). This will trigger the OpenID Connect Provider to perform a user introspection and retrieve information (specified in the scope) about the user in the form of an OpenID Connect Claim. These claims will be sent to Keystone in the form of environment variables.
Parameters: | session (keystoneauth1.session.Session) – a session object to send out HTTP requests. |
---|---|
Returns: | a token data representation |
Return type: | keystoneauth1.access.AccessInfoV3 |