-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add support for bearer token and loading token from filesystem #45
base: main
Are you sure you want to change the base?
Conversation
Thanks for the PR, @wolfv. I'll review this by EOW. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR, @wolfv. When was the support for Bearer tokens implemented into Quetz? I haven't seen any recent PR about that. Or is that something we get for free from FastAPI?
src/quetz_client/cli.py
Outdated
if token: | ||
return ApiKey(token) | ||
elif bearer_token is not None: | ||
return BearerToken(bearer_token) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does token
default to an empty string but bearer_token
defaults to None
? Why don't both default to None
?
Hey @janjagusch actually, it's not really implemented in quetz but useful in conjunction with a Google IAM Proxy. The IAM proxy takes a classic "bearer" token and then allows you to upload to quetz (when quetz is configured with the google IAP plugin that's in an open PR right now). |
No description provided.