Team,
We are running into a few issues connecting IDN as a Service Provider to a SAAS application. The configuration in IDN is simple. Provided the IDN metadata to the app owner - they provided us their metadata - added it to the configuration parameters - but it continues to throw a Failed SAML assertion - my thoughts are this configuration is no different from an app behind an F5.
Has anyone experienced issues configuring this to a SAAS application?
IDN is a Service Provider - meaning that it is an application where that is providing a service to users.
When you configure SAML with IDN, you are connecting it to an Identity Provider - an authentication “service” that confirms that an identity knows their credentials and should be able to connector to your IDN service.
You cannot configure IDN to be an Identity Provider for another application to use to validate user credentials.
Hi Alicia,
Correct - we are configuring the metadata from the SAAS application called spacexyz into IDN but it keeps giving the Failed SAML Authentication.
It worked well for an application behind the F5 but the new application is a SAAS app.
Would IDN have issues using another SAAS application as a Service Provider? The SAAS Vendor is stating ISC is the issue. See below the SAML trace
SAML-tracer-export-Sailpoint.json (52.8 KB)
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.