[jira] [Commented] (PROTON-90) SSL: provide access to the certificate provided by the peer.
[ https://issues.apache.org/jira/browse/PROTON-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13798259#comment-13798259 ] Rafael H. Schloming commented on PROTON-90: --- This feature is no longer necessary now that we do hostname authentication, and providing it would require exposing a lot of the low level details of the internal SSL implementation. For these reasons I'm going to close this as won't fix. SSL: provide access to the certificate provided by the peer. Key: PROTON-90 URL: https://issues.apache.org/jira/browse/PROTON-90 Project: Qpid Proton Issue Type: New Feature Components: proton-c Reporter: Ken Giusti Currently, the SSL implementation merely verifies that the certificate supplied by the remote is signed by the configured CA. There is no way to extract information from that certificate - such as the CN, subject, etc. It would be useful to provide an accessor api to get at the contents of the certificate. This could be used by the application to, for example, verify the CN and decide whether or not to close the connection. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (PROTON-90) SSL: provide access to the certificate provided by the peer.
[ https://issues.apache.org/jira/browse/PROTON-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504526#comment-13504526 ] Philip Harvey commented on PROTON-90: - Hi, do you have a view on how the api should be modified to achieve this? The reason I ask is so PROTON-165 can expose it in a similar way. SSL: provide access to the certificate provided by the peer. Key: PROTON-90 URL: https://issues.apache.org/jira/browse/PROTON-90 Project: Qpid Proton Issue Type: New Feature Components: proton-c Reporter: Ken Giusti Currently, the SSL implementation merely verifies that the certificate supplied by the remote is signed by the configured CA. There is no way to extract information from that certificate - such as the CN, subject, etc. It would be useful to provide an accessor api to get at the contents of the certificate. This could be used by the application to, for example, verify the CN and decide whether or not to close the connection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira