Support user scoped token for API authorization #9
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
Bump version to version 4.3. Allow specifying the BLOCKBRIDGE_API_KEY as a user-scoped token, that does not require system global access. If the token specified *is* a global "system" token, then specify BLOCKBRIDGE_GLOBAL_TOKEN="1" to change the mode of operation. With a user scoped token, no "user" is required when creating a volume or a profile. All volumes are and state are kept per-user. To use different users, use different volume plugins. Includes the following changes: * provision with "user" api token by default * rev version to v4.3 * volume_user not required for user_access_token * Create new scoped authorizations only if specified token allows it * cache lookup vol info respects when no "user" is specified * don't lookup or use "user" in api or profile if user_access_token * conditionally prefix log messages with a timestamp
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.
Bump version to version 4.3.
Allow specifying the BLOCKBRIDGE_API_KEY as a user-scoped token, that
does not require system global access. If the token specified is
a global "system" token, then specify BLOCKBRIDGE_GLOBAL_TOKEN="1" to
change the mode of operation.
With a user scoped token, no "user" is required when creating a volume
or a profile. All volumes are and state are kept per-user. To use
different users, use different volume plugins.
Includes the following changes: