Mock pouta_access_token #50
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order for the user to be able to use Keystone without having to give their password, AAI now returns a
pouta_access_tokenwhich can be exchanged for an unscoped Keystone token at/v3/OS-FEDERATION/identity_providers/oauth2_authentication/protocols/openid/auth. Here a python script starts a server at port 5001 and has the aforementioned endpoint available. It also proxies all other requests to port 5000, so the port 5001 can be used for Keystone endpoints as well. To use the mocked endpoint, give the Bearer token a token created, e.g., withopenstack token issueor get first a unscoped token with a password.