TOKEN-BASED AUTH MIDDLEWARE
This WSGI component:
Refer to: http://docs.openstack.org/developer/python-keystoneclient/ middlewarearchitecture.html
When using composite authentication (a user and service token are present) additional service headers relating to the service user will be added. They take the same form as the standard headers but add ‘_SERVICE_’. These headers will not exist in the environment if no service token is present.
json encoded keystone service catalog (optional). For compatibility reasons this catalog will always be in the V2 catalog format even if it is a v3 token.
Bases: object
Auth Middleware that handles authenticating client calls.
Bases: exceptions.Exception
Bases: exceptions.Exception
Bases: exceptions.Exception
Bases: exceptions.Exception
Returns a WSGI filter app for use with paste.deploy.
Starting point for routing EC2 requests.
Bases: object
Authenticate an EC2 request with keystone and convert to token.
Returns a WSGI filter app for use with paste.deploy.
Return a list of oslo.config options available in auth_token middleware.
The returned list includes all oslo.config options which may be registered at runtime by the project.
Each element of the list is a tuple. The first element is the name of the group under which the list of elements in the second element will be registered. A group name of None corresponds to the [DEFAULT] group in config files.
This function is also discoverable via the entry point ‘keystonemiddleware.auth_token’ under the ‘oslo.config.opts’ namespace.
The purpose of this is to allow tools like the Oslo sample config file generator to discover the options exposed to users by this middleware.
Returns: | a list of (group_name, opts) tuples |
---|
S3 TOKEN MIDDLEWARE
This WSGI component:
Bases: object
Auth Middleware that handles S3 authenticating client calls.
Bases: exceptions.Exception
Returns a WSGI filter app for use with paste.deploy.