If E-Signature is active, configure the Identity Provider form and add the Assertion Consumer URL for e Signature authentication field.
In most cases, this URL will be: https://YOURINSTANCE.service-now.com/
After multi-provider SSO is configured, you can send a URL to your users with the correct Id P in the parameter string.
For example: After a user successfully logs in to the Id P page, a cookie containing the Id P sys_id is added to the browser.
The necessary SAML settings are migrated to the Multi-Provider SSO application into the SAML2 Migrated table.
You can still modify items like the x509 certificate, Id P details, and so on through the Multi-Provider SSO application.
Note: This article applies to Fuji and earlier releases.
For more current information, see Multiple-Provider Single Sign-On (SSO) at Service Now Wiki is no longer being updated. The multiple provider single sign-on feature allows organizations to use several SSO identity providers (Id Ps) to manage authentication as well as retain local database (basic) authentication.
Alternatively, a company might implement SAML 2.0 and a digest token authentication solutions on the same instance.
The next time the user attempts to log in to the Service Now system, the system redirects the user to log in to the Id P server, which automatically logs in to the Service Now system.
If a URL parameter is not set or the browser cache has been cleared, users can also do the following: After users successfully log in to an Id P, they are automatically redirected to that Id P whenever they attempt to access the Service Now instance.
Warning: If you clone your instance, preserve the multiple provider SSO properties on the target instance for all of the properties tables that are installed with multi-provider SSO.
This is recommended for all targeted instances that have multi-provider SSO enabled.
Note: The test connection user interface only works for identity providers that support displaying content in a frame.