-
Notifications
You must be signed in to change notification settings - Fork 184
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
document why we mint an x-access-token header #1434
Comments
@butonic this is an old issue that was transferred from the archived |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
closing in favor of #4701 |
we mint our own token after authenticating the request.
internal services use that token to authenticate requests
reva uses x-access-token for the same thing
we reuse that token, so the reva gateway does not have to reauthenicate using oidc
The text was updated successfully, but these errors were encountered: