Skip to main content

PingFederate SSO 404 error

Looking for PingFederate OAuth errors instead?

This page covers a 404 error in PingFederate SAML SSO for logging into Atlan. For OAuth errors (audience mismatch, invalid access token, signature invalid, user not found) when querying Snowflake from Atlan Insights, see Troubleshooting PingFederate OAuth.

Why do I get 404 errors when using PingFederate SSO?​

If you're encountering a 404 error while using PingFederate single sign-on (SSO), it's possible that the authentication request requires a signed assertion.

To reconfigure the signature policy:

  • Navigate to the Signature Policy tab in PingFederate and uncheck the Always Sign Assertion box.

image__34_.png
By disabling the Always Sign Assertion setting, the authentication request can proceed without requiring a signed assertion.

If you encounter any further issues or have questions, refer to the PingFederate documentation or contact Atlan support for assistance.