Adding support for Bearer Token (OAuth2) #49
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.
Using oauth2proxy it is not difficult to configure ELOG to authenticate users based on IAM client.
Unfortunately, passing through the proxy with this python client requires adding a header including the Bearer token generated by the user interacting with the IAM.
This pull request introduces an additional argument to the constructor of the elog object to pass an access token.
Since the client application may have it's own workflow to keep the access token updated, the argument can be a callable, in which case it is called to retrieve the token at each call.
Example.