Bases: fixtures.fixture.Fixture
A fixture that will stub out all plugin loading calls.
When using keystoneauth plugins loaded from config, CLI or elsewhere it is often difficult to handle the plugin parts in tests because we don’t have a reasonable default.
This fixture will create a TestPlugin
that will be
returned for all calls to plugin loading so you can simply bypass the
authentication steps and return something well known.
token (str) – The token to include in authenticated requests.
endpoint (str) – The endpoint to respond to service lookups with.
user_id (str) – The user_id to report for the authenticated user.
project_id (str) – The project_id to report for the authenticated user.
Utility function to get the endpoint the plugin would return.
This function is provided as a convenience so you can do comparisons in your tests. Overriding it will not affect the endpoint returned by the plugin.
path (str) – The path to append to the plugin endpoint.
Prepare the Fixture for use.
This should not be overridden. Concrete fixtures should implement _setUp. Overriding of setUp is still supported, just not recommended.
After setUp has completed, the fixture will have one or more attributes which can be used (these depend totally on the concrete subclass).
MultipleExceptions if _setUp fails. The last exception captured within the MultipleExceptions will be a SetupError exception.
None.
The recommendation to override setUp has been reversed - before 1.3, setUp() should be overridden, now it should not be.
BaseException is now caught, and only subclasses of Exception are wrapped in MultipleExceptions.
Bases: keystoneauth1.plugin.BaseAuthPlugin
A simple plugin that returns what you gave it for testing.
When testing services that use authentication plugins you often want to stub out the authentication calls and focus on the important part of your service. This plugin acts like a real keystoneauth plugin and returns known standard values without having to stub out real keystone responses.
Note that this plugin is a BaseAuthPlugin and not a BaseIdentityPlugin. This means it implements the basic plugin interface that services should be using but does not implement get_auth_ref. get_auth_ref should not be relied upon by services because a user could always configure the service to use a non-keystone auth.
token (str) – The token to include in authenticated requests.
endpoint (str) – The endpoint to respond to service lookups with.
user_id (str) – The user_id to report for the authenticated user.
project_id (str) – The project_id to report for the authenticated user.
Return an endpoint for the client.
There are no required keyword arguments to get_endpoint
as a plugin
implementation should use best effort with the information available to
determine the endpoint. However there are certain standard options that
will be generated by the clients and should be used by plugins:
service_type
: what sort of service is required.
service_name
: the name of the service in the catalog.
interface
: what visibility the endpoint should have.
region_name
: the region the endpoint exists in.
session (keystoneauth1.session.Session) – The session object that the auth_plugin belongs to.
The base URL that will be used to talk to the required service or None if not available.
string
Return the project id that we are authenticated to.
Wherever possible the project id should be inferred from the token however there are certain URLs and other places that require access to the currently authenticated project id.
session (keystoneauth1.session.Session) – A session object so the plugin can make HTTP calls.
A project identifier or None if one is not available.
str
Obtain a token.
How the token is obtained is up to the plugin. If it is still valid it may be re-used, retrieved from cache or invoke an authentication request against a server.
There are no required kwargs. They are passed directly to the auth plugin and they are implementation specific.
Returning None will indicate that no token was able to be retrieved.
This function is misplaced as it should only be required for auth plugins that use the ‘X-Auth-Token’ header. However due to the way plugins evolved this method is required and often called to trigger an authentication request on a new plugin.
When implementing a new plugin it is advised that you implement this method, however if you don’t require the ‘X-Auth-Token’ header override the get_headers method instead.
session (keystoneauth1.session.Session) – A session object so the plugin can make HTTP calls.
A token to use.
string
Return a unique user identifier of the plugin.
Wherever possible the user id should be inferred from the token however there are certain URLs and other places that require access to the currently authenticated user id.
session (keystoneauth1.session.Session) – A session object so the plugin can make HTTP calls.
A user identifier or None if one is not available.
str
Invalidate the current authentication data.
This should result in fetching a new token on next call.
A plugin may be invalidated if an Unauthorized HTTP response is returned to indicate that the token may have been revoked or is otherwise now invalid.
True if there was something that the plugin did to invalidate. This means that it makes sense to try again. If nothing happens returns False to indicate give up.
bool
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.