# AD Connector troubleshooter - wrong thumbprint for the Local Certificate

**URL:** <https://community.auth0.com/t/ad-connector-troubleshooter-wrong-thumbprint-for-the-local-certificate/12009>\
**Category:** Get Help\
**Created:** [May 31, 2018, 12:41pm UTC](https://community.auth0.com/t/ad-connector-troubleshooter-wrong-thumbprint-for-the-local-certificate/12009 "2018-05-31T12:41:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![timothy.sibley](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@timothy.sibley](https://community.auth0.com/u/timothy.sibley)\
**Post date:** [May 31, 2018, 12:41pm UTC](https://community.auth0.com/t/ad-connector-troubleshooter-wrong-thumbprint-for-the-local-certificate/12009/1 "2018-05-31T12:41:34Z")

</div>

Hi,  
I have been creating a POC of Auth0 and AD using AWS and have run into an issue with the troubleshooter.  
We are trying to use the troubleshooter script to confirm the automated installation has been successful.  
The troubleshooter always returns a certificate thumbprint miss-match between the local and server certificates.  
Having checked the server certificate thumbprint listed for the connector in the API and the thumbprint of the local certificate cert.pem in certs folder they all seem to be correct.  
The troubleshooter is returning a different thumbprint. Upon investigation i am receiving a similar error to that listed here:

> <https://github.com/leandrob/thumbprint/pull/2>
>
> Hello,
> compared to the Java implementation, the binary string produces a differ…ent result. 
> Using the \*\*buffer directly\*\* yields the same result as the Java (1.8) implementation.
> 
> Java Implementation Example:
> 
> \`\`\`java
> public String calculate(java.security.cert.X509Certificate cert) throws CertificateEncodingException {
> MessageDigest md = MessageDigest.getInstance("SHA-1");
> byte\[\] der = cert.getEncoded();
> md.update(der);
> byte\[\] digest = md.digest();
> return DatatypeConverter.printHexBinary(digest).toLowerCase();
> }
> \`\`\`
> 
> This Java Implementation returns the same thumbprint (fingerprint) hexstrings as the Java keytool when listing a keystore.
> 
> Best regards

In the deployed node-modules for the thumbprint module removing the .toString(‘binary’) causes the correct thumbprint to be returned and the troubleshooter to run without issue.

---

<div class="post-metadata">

**Author:** ![James.Morrison](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/james.morrison/32/13507_2.png) [@James.Morrison](https://community.auth0.com/u/James.Morrison)\
**Post date:** [December 18, 2018, 9:50pm UTC](https://community.auth0.com/t/ad-connector-troubleshooter-wrong-thumbprint-for-the-local-certificate/12009/3 "2018-12-18T21:50:31Z")

</div>

Hey there @timothy.sibley,

As it has been more than a few months since this topic was opened and there has been no reply or further information provided from the community as to the existence of the issue we would like to check if you are still facing the described challenge?

We are more than happy to assist in any way! If the issue is still out there please let us know so we can create a new thread for better visibility, otherwise we’ll close this one in week’s time.

Thank you!

---

<div class="post-metadata">

**Author:** ![James.Morrison](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/james.morrison/32/13507_2.png) [@James.Morrison](https://community.auth0.com/u/James.Morrison)\
**Post date:** [December 25, 2018, 1:50pm UTC](https://community.auth0.com/t/ad-connector-troubleshooter-wrong-thumbprint-for-the-local-certificate/12009/4 "2018-12-25T13:50:35Z")

</div>

This topic was automatically closed 6 days after the last reply. New replies are no longer allowed.
