[ https://issues.apache.org/jira/browse/AMQ-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
rajiv devaraj reopened AMQ-7277: -------------------------------- I have a scenario where , server maintain different self signed certificates for different clients , so while SSL handshake there are exchange of certificates will be different for different client , so this will not be achievable if i have multiple certificates present . If you take a look at SSLSocket they have an api addHandshakeCompletedListener , from where we can fetch both Local Certificates & Peer Certificates exchanged during the handshake . [https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/SSLSocket.html] and from handshakecompleted event we can get both Local Certificate & Peer Certificate that got exchanged . [https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/HandshakeCompletedEvent.html] Similarly i would you like to have information on getting both LocalCertificate & peerCertificate that got exchanged during the successful handshake > Need to expose an api to extract localCertificates & PeerCertificates during > the handshake > ------------------------------------------------------------------------------------------ > > Key: AMQ-7277 > URL: https://issues.apache.org/jira/browse/AMQ-7277 > Project: ActiveMQ > Issue Type: New Feature > Affects Versions: 5.7.0 > Reporter: rajiv devaraj > Priority: Major > Fix For: 5.7.0, 5.15.8, 5.15.9, 5.15.11 > > > Like in 5.15.11 , where under Tranport > interface(org.apache.activemq.transport) there is a way to extract peer > certificate exchanged during the handshake , like wise i would need to know > the local certificate being exchanged during the handshake . so would require > an api to extract both localCerticate & peerCertificate being exchanged > during the communication > > attaching the stack overflow link for more reference : > [https://stackoverflow.com/questions/57507718/socket-where-we-have-api-to-fetch-local-certificates-peer-certificates-during?noredirect=1#comment101492217_57507718] -- This message was sent by Atlassian Jira (v8.3.2#803003)