-
Notifications
You must be signed in to change notification settings - Fork 112
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
Add logging for certificate errors #10818
Conversation
@@ -137,6 +137,7 @@ def capture_analytics | |||
# Logging to indicate if a validation bug fix will create a potentially breaking change | |||
analytics_payload[:encryption_cert_matches_matching_cert] = | |||
encryption_cert_matches_matching_cert? | |||
analytics_payload[:cert_error_details] = saml_request.cert_errors |
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.
i thought about using the existing error_details
key, since it should be empty if the request is successful. but i thought that could be confusing ultimately, so decided not to -- interested in thoughts about that!
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.
it makes sense to me to keep separate!
matching_cert_serial:, | ||
encryption_cert_matches_matching_cert:, | ||
} | ||
end |
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.
i removed this to make the result conditions more explicit in the individual tests
93ed624
to
99e7dde
Compare
* changelog: Internal, Metrics, Add certificate validation errors to event
🎫 Ticket
https://gitlab.login.gov/lg-people/lg-people-appdev/Melba/backlog-fy24/-/issues/42
🛠 Summary of changes
cert_error_details
to log specific certificate errors if the request is signed and successful