Multiple portal login pages

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2017 06:55 AM
Hi, can someone confirm the default behaviour of SN for me regarding multiple Portals?
We're planning on having many portals - one for each client. Ideally every portal should have its own login page - it seems you can set it up like that. The question is, is the non-logged in user automatically redirected to the correct portal login page? e.g.
User A enters URL https://instance.service-now.com/PortalA -> they should get login page of Portal A
User B enters URL https://instance.service-now.com/PortalB -> they should get login page of Portal B
Or do we need to tamper with default login script includes? I should add that our platform is domain separated.
Also, do you know of any way how to disable non-role users fro accessing the application (only allow them to see portal pages)? Meaning if someone deletes the portal part from the URL, they should either see an error page or get redirected back to the portal...
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-26-2017 09:59 PM
Recently we have similar kind of requirement so, we just tampered the default login script to track the how the user are login to ServiceNow, but ours is standalone instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2017 02:25 PM
Thanks, I am still hoping there might be a less invasive way to achieve this though... anyone?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2017 06:06 AM
Tomasz,
Did you get your answer?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-07-2017 04:56 AM
Hi Blair,
this is probably water under the bridge now but there does not seem to be a nice way of doing that. What I ended up with:
1. If end user goes to instance.service-now.com/portalsuffix as non-logged in, they end up on that portal's login page - this is OOTB.
2. We have reverse proxies set up e.g. ourname.com/portalsuffix with rules saying that if a user removes the portalsuffix part from URL, they will get redirected to ourname.com/portalsuffix anyway.
3. login scrpt would not work in ur case as we have a domin-separated environment with multiple portals and you can only specify one redirect URL within that script.
4. You could experiment with Installation Exit - Login script but I could not get it to redirect a user to a specific page...