Skip to content
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

Enable forwarding of original authorization header to (remote) authorizer #528

Closed
catper opened this issue Sep 29, 2020 · 4 comments
Closed
Assignees
Labels
feat New feature or request.
Milestone

Comments

@catper
Copy link
Contributor

catper commented Sep 29, 2020

Is your feature request related to a problem? Please describe.

Authorization is typically done on the subject but there may be additional information in the access token that is needed for a decision to be made. At present, it doesn't seem possible to forward the original access token to a remote authorizer though, you can only forward data that exists within the authSession object can be passed on.

Describe the solution you'd like

I'd like the auth header to be forwarded to the remote authorizer.

@aeneasr
Copy link
Member

aeneasr commented Sep 30, 2020

Thank you! This makes definite sense and will be part of #441 once we work on it :)

@aeneasr aeneasr added this to the v0.39.0 milestone Sep 30, 2020
@aeneasr aeneasr self-assigned this Sep 30, 2020
@aeneasr aeneasr added the feat New feature or request. label Sep 30, 2020
@catper
Copy link
Contributor Author

catper commented Sep 30, 2020

While waiting for #441 to happen, would it be acceptable to implement this as "stand alone" feature? I'm thinking all that's needed is a single line, copying the auth header and then we'd be done?

@ashneverdawn
Copy link

I'm interested in this too.

@aeneasr
Copy link
Member

aeneasr commented Oct 6, 2020

Yes, sounds good! Open to contributions! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request.
Projects
None yet
Development

No branches or pull requests

3 participants