-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
OAuth2 filter: supports forwarding ID tokens to upstream web service via the Authorization header bearer scheme #32805
Comments
I think this issue can help me with my case. I want save Authorization Header from request. But if |
👀 Hi guys, any update on this one? |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
How does this relate to |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
Title: OAuth2 filter: supports forwarding ID tokens to upstream web service via the Authorization header bearer scheme
Description:
OAuth2 filter has a
forward_bearer_token
configuration knob. If enabled, it forwards access tokens to the upstream web service via the Authorization header bearer scheme. Could we also add a knob to forward ID tokens via the Authorization header? This would allow the JWT filter or applications to utilize ID tokens for JWT-based authentication or other authorization purposes.Related discussion in Envoy Gateway: envoyproxy/gateway#2425 (comment)
The text was updated successfully, but these errors were encountered: