token: pass the project id to get the catalog #1
Conversation
This file contains hidden or 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
Keystone returns the service catalog only with the scoped token. If the user has no default project and we don't pass a project_id, we end up in the case where the token is unscoped. By passing the project id, we ensure the token is scoped. Note, the behaviour is not recent, it was already the case OpenStack Havana. From the changelog: https://docs.openstack.org/api-ref/identity/v3/#service-catalog-and-endpoints A token without an explicit scope of authorization is issued if the user does not specify a project and does not have authorization on the project specified by their default project attribute See: https://docs.openstack.org/api-ref/identity/v3/#service-catalog-and-endpoints
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Keystone returns the service catalog only with the scoped token. If the
user has no default project and we don't pass a project_id, we end up
in the case where the token is unscoped.
By passing the project id, we ensure the token is scoped.
Note, the behaviour is not recent, it was already the case OpenStack
Havana. From the changelog:
See: https://docs.openstack.org/api-ref/identity/v3/#service-catalog-and-endpoints