-
Notifications
You must be signed in to change notification settings - Fork 41.1k
authentication: show more details when cert verification fails #130137
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
authentication: show more details when cert verification fails #130137
Conversation
Alongside serial number log line should include common name and issuer so that invalid certificate would be easier to identify. Hopefully this information is not considered sensitive and it can appear in log lines and error messages
Hi @vrutkovs. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vrutkovs The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
/cc @enj |
/test pull-kubernetes-unit |
/hold This is not a bug, the CN is not logged by design. |
oh well |
/triage accepted |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Alongside serial number log line should include common name and issuer so that invalid certificate would be easier to identify. Hopefully this information is not considered sensitive and it can appear in log lines and error messages
Which issue(s) this PR fixes:
Fixes #129600
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: