feat: Improve logging in the oauth2 callback handler #11370
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #11369
Motivation
The current implementation of the OAuth2 callback handler lacks sufficient logging, making it difficult to identify errors and misconfigurations related to SSO (Single Sign-On). By adding detailed logs, we can simplify the process of configuring SSO and troubleshoot any issues that may arise.
Due to the insufficient logs in the oauth2 callback handler, it wasn't easy to identify the errors and misconfigurations about sso.
If the servers writes detailed logs, it would help the process configuring sso.
Modifications
I have added error logging to the
/oauth2/callback
handler.Verification
To verify these changes, I performed the following tests:
foobarbaz
, which is an invalid value.