Skip to main content
July 2, 2024
Solved

Clarification on Single Sign-On Implementation and Certificate Management

  • July 2, 2024
  • 3 replies
  • 0 views

Requirement:

  • Implement Single Sign-On (SSO) for your application.
  • Updated the Service Provider Signing Certificate in Appian.
  • Generated a metadata file and sent it to clients.
  • Configured the file and received an "Identity Provider Metadata" file, which was then configured in Appian under "Identity Provider Information".

Questions:

  1. If I change the certificate that is already configured on the Appian side, will SSO authentication fail due to a metadata mismatch?

  2. If it should fail due to a certificate change, why is it that in my case, when I change the certificates on the Appian side, the SSO works fine, and I am able to sign in to the website? The certificates are generated by the IIS manager on my system.

Best answer by yogip3177

Maybe your IdP is configured to not validate SAML request signatures. Check your IdP configuration.


3 replies

yogip3177Answer
July 2, 2024

Maybe your IdP is configured to not validate SAML request signatures. Check your IdP configuration.


July 3, 2024

In my SAML response, I see schemas.microsoft.com/.../x509. This indicates that the IdP used an X.509 certificate for authentication. Do I need to add any additional certificates on my side besides the SAML configuration?

4o