Feature: connection information to aid debugging Mutual TLS

[ewilde]

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

[fredsted]

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 [email protected] 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.