I'm attempting to set up SAML authentication using Azure AD. Azure AD offers Service Provider Signing certificates in three formats and I carefully selected .pem. When I try to upload it to my app in the "Add SAML Identity Provider" screen, I received the following error - The provided PEM file is not valid for certificate authentication. Missing: Private Key. Is this an Appian issue? It's hard to believe that something as widely deployed as Azure AD would be providing misconfigured certificates. What am I missing?
Phil
Discussion posts and replies are publicly visible
Oops, my mistake. I was attempting to upload the Identity Provider (Azure AD) Certificate to the Service Provider Signing Certificate.
PK I have the same question what was the issue?
You need a PEM file that has a Certificate and a Private Key (i had to concatenate 2 strings into one file). That file can be obtained from a SSL provider (it's not obtained from Azure AD).
Hope it helps.
@Ignado, If this should not be obtained from Azure AD, how do we update the private key both on Azure AD and Appian application pls? Azure AD SSO SAML provides .PEM, .CRT of RAW and BASE64 file to configure it on SP side. Not sure as I get the same error as mentioned on this post description. Can you pls suggest? Thanks.