How to enable seamless sso login to users when multiple IDPs are activated?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2024 08:47 PM - edited 12-17-2024 08:48 PM
We have different set of users and have 3 different identity providers say X, Y, Z.
User set A - should use 'X' IDP
User set B - should use 'Y' IDP
User set C - should use 'Z' IDP
The moment respective users from A or B or C hit https://XXXXXX.service-now.com
it should automatically take them to respective IDPs for authentication.
How can I do it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 09:12 PM
Anyone..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2024 01:54 AM
No one?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2025 04:48 AM
Hi @Suggy
This feature is not yet available OOB in servicenow, but this is going to be available in the upcoming future releases (can't commit on the timeline though).
You can add it into the IDEA Portal or vote for this if there is an existing entry for this idea.
I had one followup question though - when you mentioned -
The moment respective users from A or B or C hit https://XXXXXX.service-now.com
it should automatically take them to respective IDPs for authentication.
You mean if the user enters his username on login page, then only based on the username, it will decide which IDP it will redirect to. Is this correct understanding?
If yes, then based on the above assumption, you can customize the login scripts to achieve this.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2025 10:09 AM
Scenario is - In user table, we have users from company 'A', company 'B', Company 'C'.
Their user ID are like:
Say we have 3 different Identity providers configured - one for a.com users (IDP1), one for b.com users (IDP2) one for c.com users (IDP3)
When user from a.com hits https://XXXXXX.service-now.com, it should take to IDP1 page automatically.
When user from b.com hits https://XXXXXX.service-now.com, it should take to IDP2 page automatically.
When user from c.com hits https://XXXXXX.service-now.com, it should take to IDP3 page automatically.