We can support any IdP that supports the SAML 2.0 protocol. Clients that have done previous integrations have used Okta, PingFederate, and AzureAD as well as several others.
Yes, if a logout URL is provided in the SAML Metadata we can support SLO.
Yes, multi-factor authentication is supported if it is managed by the Identity Provider.
We can support any NameID format the IdP is configured to support. Customers will use email addresses or GUIDs.
RelayState identifies the internal site the user should be directed to after authentication. If the correct RelayState is not returned, Radancy may not be able to identify the intended internal career site and users will be redirected to the Radancy Portal.
Yes, we can support encrypted SAML responses if required.
We can support signed SAML Auth Requests but typically do not. There are configuration limitations with Okta and PingFederate that require configuration changes on the IdP side.
We currently do not support Just In Time provisioning for user accounts.
We support HTTP Post and HTTP Redirect bindings. We do not support HTTP Artifact binding.
No. Authorization is role-based and controlled by Radancy via an admin tool.
No. Users must be provisioned in the Radancy Platform and given the appropriate application permissions. SSO is used to authenticate the user.
Yes, multiple SSO integrations can use the same Identity Provider URL. Separate integrations should use unique IdP issuers when they need to be managed independently.
No. Radancy's Entity ID is static and cannot be customized for an individual SSO integration.
Confirm whether the IdP URL, signing certificate, issuer, or SAML metadata has changed. If so, provide Radancy with the updated metadata and details of the change.