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

oauth: always set token cookies in response regardless of forward_bearer_token option #34156

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

derekargueta
Copy link
Member

@derekargueta derekargueta commented May 15, 2024

Commit Message: oauth: always set token cookies in response regardless of forward_bearer_token option
Additional Description: Unconditionally set the BearerToken, IdToken, and RefreshToken cookies in the response. The documentation of forward_bearer_token states "Forward the OAuth token as a Bearer to upstream web service." It's confusing for this behavior to affect response cookies as well and I can't think of a benefit that's being achieved here. This brings the behavior of this filter more aligned with what the documentation describes.
Risk Level: Low
Testing: Included
Docs Changes: N/A
Release Notes: Included
Platform Specific Features: N/A
Fixes: #32566 #15489

…rer_token option

Signed-off-by: Derek Argueta <darguetap@gmail.com>
Signed-off-by: Derek Argueta <darguetap@gmail.com>
Signed-off-by: Derek Argueta <darguetap@gmail.com>
Signed-off-by: Derek Argueta <darguetap@gmail.com>
@derekargueta derekargueta marked this pull request as draft May 19, 2024 20:03
Signed-off-by: Derek Argueta <darguetap@gmail.com>
Signed-off-by: Derek Argueta <darguetap@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OAuth2 Filter - Unexpected behaviour of forward_bearer_token
2 participants