-
Notifications
You must be signed in to change notification settings - Fork 390
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
Feature: connection information to aid debugging Mutual TLS #75
Comments
Hi Edward, that sounds like it would be a great addition to Webhook.site. I’d welcome any work on this.
… On 19 Aug 2019, at 13.07, Edward Wilde ***@***.***> wrote:
Some platforms support mutual TLS for authenticating webhooks
Example of these platforms might be:
https://api.slack.com/docs/verifying-requests-from-slack#mutual_tls
https://www.sparkpost.com/docs/tech-resources/webhook-authentication/
Debugging
Sometimes it's useful to know the details of the client certificate being sent:
Subject Alternative Name , Subject Common Name etc...
Proposal
If a client certificate has been presented during TLS handshake present this information in a new information panel
I'm happy to work on this if it meets with the projects goals
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some platforms support mutual TLS for authenticating webhooks
Example of these platforms might be:
Debugging
Sometimes it's useful to know the details of the client certificate being sent:
Subject Alternative Name
,Subject Common Name
etc...Proposal
I'm happy to work on this if it meets with the projects goals
The text was updated successfully, but these errors were encountered: