[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24312: ------------------------------------------ [~rhit_mchappell] thanks for looking this up! Turns out that the bug is on our side of the trenches. There are basically 2 problems in our implementation: * the code was flawed when it comes to parsing SSL certificates. It was not using the effective serial number but was erroneously parsing and extracting it when looking into the certificate * the code was basically creating it's own rules to decide whether 2 certificates are identical. It was extracting info, storing them and comparing those to the infos a new certificate that it gets presented. So the work for this issue is to get back to the jdk classes for ssl certificates and let them decide whether 2 certificates are identical. Resulting from this is that we need to store the effective certificate, not values that were extracted from previous certificates. -- This message was sent by Atlassian JIRA (v7.2.3#72005)