# Importing certificate for SAML connection setup is returning invalid certificate message (md5?)

**URL:** <https://community.auth0.com/t/importing-certificate-for-saml-connection-setup-is-returning-invalid-certificate-message-md5/24066>\
**Category:** Get Help\
**Tags:** samlp, saml\
**Created:** [April 16, 2019, 7:56pm UTC](https://community.auth0.com/t/importing-certificate-for-saml-connection-setup-is-returning-invalid-certificate-message-md5/24066 "2019-04-16T19:56:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dclark](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dclark/32/10810_2.png) [@dclark](https://community.auth0.com/u/dclark)\
**Post date:** [April 16, 2019, 7:56pm UTC](https://community.auth0.com/t/importing-certificate-for-saml-connection-setup-is-returning-invalid-certificate-message-md5/24066/1 "2019-04-16T19:56:38Z")

</div>

Hi folks!  
I am attempting to setup a SAMLP Identity Provider connection with a city IT department. I have the sign in url etc but when I upload the X509 certificate they provided me, auth0 is telling me invalid certificate. I have installed the certificate in the store on my machine and it looks valid. The only off thing I see is the certificate looks like it was signed with md5 hashing algorithm. Is this why Auth0 is not allowing it? If so is there a way to get this cert in there and connected? If not, what other possible reasons or debugging could I check to see why it doesn’t like the cert?

---

<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:** [April 22, 2019, 4:15pm UTC](https://community.auth0.com/t/importing-certificate-for-saml-connection-setup-is-returning-invalid-certificate-message-md5/24066/2 "2019-04-22T16:15:43Z")

</div>

Hey there @dclark and welcome to Auth0’s Community!

On the problem at hand, It’s very likely you are running into an issue with how the X509 is encoded. We actually have a terrific doc that I’ve listed below that dives into the whole process. When you get a minute give it a look and it should aid you in your quest. In the chance it doesn’t, please let me know what you feel it is missing so we can work to adjust it accordingly. Thanks!

> - **X509 Signing Certificate** : The signing certificate (encoded in PEM or CER) provided by the identity provider

[https://auth0.com/docs/connections/enterprise/samlp](https://auth0.com/docs/connections/enterprise/samlp)

---

<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:** [May 6, 2019, 8:15pm UTC](https://community.auth0.com/t/importing-certificate-for-saml-connection-setup-is-returning-invalid-certificate-message-md5/24066/4 "2019-05-06T20:15:49Z")

</div>

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