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

DM-41075: Log OIDC exceptions properly #870

Merged
merged 2 commits into from
Oct 6, 2023
Merged

DM-41075: Log OIDC exceptions properly #870

merged 2 commits into from
Oct 6, 2023

Conversation

rra
Copy link
Member

@rra rra commented Oct 6, 2023

Rather than just raising exceptions during various OIDC provider parse errors, also log those exceptions. Include the body of the response from the token URL if we cannot parse it as valid JSON, since hopefully the chances that it contains secure information are low in that case.

@rra rra force-pushed the tickets/DM-41075 branch 3 times, most recently from c3b58d0 to 6fb3e15 Compare October 6, 2023 15:34
@rra rra marked this pull request as ready for review October 6, 2023 15:34
@rra rra changed the title DM-41075: Log failed OIDC response from token URL DM-41075: Log OIDC exceptions properly Oct 6, 2023
Rather than just raising exceptions during various OIDC provider
parse errors, also log those exceptions. Include the body of the
response from the token URL if we cannot parse it as valid JSON,
since hopefully the chances that it contains secure information are
low in that case.
Useful for debugging network and HTTP request issues.
@rra rra merged commit f741aab into main Oct 6, 2023
5 checks passed
@rra rra deleted the tickets/DM-41075 branch October 6, 2023 16:00
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.

None yet

1 participant