Multi provider SSO - Access via base URL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-30-2016 06:58 AM
Hi,
Ive recently installed the Multi provider SSO plugin on Eureka. Previously had the SAML 2.0 setup working and have managed to get the new multi working between me and the Identity provider admin.
When applying this to live I want to make it seamless from an end user point of view. Currently in live (using old SAML 2.0 single the end user enters the base url (http://xxx.service-now.com) and gets logged in via the SSO. Having read the following wiki article is this still possible to achieve? I want to avoid having to give the end users (30k +) a newly created URL (as per below article extract).
Is it possible to make a seamless switch over? If so..any advice or direction would be appreciated.
:
Multiple Provider Single Sign-On - ServiceNow Wiki
--------------------------------------------------------------------
5 Logging In
The recommended and most efficient method for users to log in using multi-provider SSO is to use a specifically configured URL. After multi-provider SSO is configured, you can send a URL to your users with the correct IdP in the parameter string. For example:
- /login_with_sso.do?glide_sso_id=<sys_id of the sso configuration>
After a user successfully logs in to the IdP page, a cookie containing the IdP sys_id is added to the browser. The next time the user attempts to log in to the ServiceNow system, the system redirects the user to log in to the IdP server, which automatically logs in to the ServiceNow system.
If a URL parameter is not set or the browser cache has been cleared, users can also do the following:
- Click the Use external login link on the ServiceNow login page.
- The external login page appears. Users can click Use local login to return to the standard ServiceNow login page.
- Enter the value for the specified field on the user table that you configured in Multi-Provider SSO properties.
- The user is redirected to the IdP server, where they log in.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-30-2016 08:39 AM
The Service-Now base URL would still work. I am using the Multiprovider SSO Plugin with Siteminder.
The user puts in the base login link and the link redirects to the IDP login screen if not already logged into the IDP. If already logged in, the link would take the user to the instance home screen.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-30-2016 08:57 AM
Thanks for the reply.
It seems only once they have logged in once to the new Idp with the constructed url as per sn wiki that it's cached on their browser and sure when they try standard site they're logged in.
Sent from my iPhone
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-30-2016 11:03 AM
That's my point, i didn't have to construct a URL, it behaved in this fashion right after the implementation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-30-2016 11:07 AM
Ok. Logged a call with hi. Reading the wiki only mentions the best way to login on is by providing users with the url with sso sys id as mentioned before.
Sent from my iPhone