This message appears when uploading an external CA certificate to the sistem. "Only self signed CA certificates can have identical subject and issuer fields". It's a Microsoft-adfs autosigned CA certificate used to sign SAML messages and we can't not change that, you know if there's any way to upload this certificate to the system in order we can use it? thanks!
Ok, so it seems lots of people would have this problem since self signed certs for SAML Identity providers are probably best practice. (We started with a CA signed cert but then after doing certificate rollover with 40+ service providers a year and a half later decided this was insane.)
Palo Alto support tells me to either use a CA cert or generate a new cert in PaloAlto. Either way would force me into the certificate rollover process with all my service providers) Did anyone ever figure out a trick or workaround for this? This thread is not auspicious.
Thanks for replying, I really appreciate it. As to the workaround, maybe I am dense, but I dumped out the xml and reviewed the <certificate> block. Each existing certificate is present and I can see how to change the the <ca></ca> flag, but since I can't import the certificate I need, it is not in this section. I thought I could just manually add the needed certificate to this section since I have the PEM encoded public key for the certificate, and I can pull most of the fields from the cert, but I was stumped by the subject and issuer hash tags, since I am not aware of what hashing algorithm they are using. (See below for an example CA entry.)
I admit, I must be missing something obvious, can you guide me in the error of my ways?
<not-valid-before>Oct 22 12:00:00 2013 GMT</not-valid-before>
<issuer>/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV Root CA</issuer>
<not-valid-after>Oct 22 12:00:00 2028 GMT</not-valid-after>
<common-name>DigiCert SHA2 High Assurance Server CA</common-name>
<subject>/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CA</subject>
No, sorry if this was not clear. As I noted, this is just an example certificate from an existing CA taken from the XML config export. Since I can't import the certificate I need to add through the GUI, it is not in the export to tweak.
I included the example section to illustrate the fields you would need to have to manually create a certificate entry and import the config. I think I could put correct values in for most of them but am stumped by what hashing algorithm PaloAlto is using to generate the
But maybe I don't need to go down this path. Do you know of another way?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!