-
Notifications
You must be signed in to change notification settings - Fork 978
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
feat: log claims #3798
feat: log claims #3798
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only setting the keys should not leak any PII.
CI fails |
b6e0bc5
to
a8e3475
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3798 +/- ##
=======================================
Coverage 78.14% 78.14%
=======================================
Files 349 349
Lines 24118 24121 +3
=======================================
+ Hits 18846 18849 +3
Misses 3852 3852
Partials 1420 1420 ☔ View full report in Codecov by Sentry. |
s.forwardError(w, r, req, s.handleError(w, r, req, pid, nil, err)) | ||
return | ||
} | ||
|
||
span.SetAttributes(attribute.StringSlice("claims", maps.Keys(claims.RawClaims))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't this leak PII into the tracing system?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this is just the keys, meaning the claim keys. The PII is just in the values, which we don't send.
Sometimes there are issues with mapping the claims from a SSO provider to an identity trait. This change adds the claims that we get back to the event, so that we can better debug these issues.
Related issue(s)
Checklist
introduces a new feature.
contributing code guidelines.
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got the approval (please contact
[email protected]) from the maintainers to push
the changes.
works.
Further Comments