
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2019 10:07 AM
After we upgraded to London our users started being redirected back to the Service Portal home page when logging in from Catalog items, or other pages within the portal.
This is less than ideal and many of our users are now complaining.
However, I have been through several articles, documentation and videos and made several attempts to correct this. I am finding nothing in our setup that would have broken this. It appears that it should work, but I am not having any luck.
- SPEntryPage appears good
- glide.entry.first.page.script is set to "new SPEntryPage().getFirstPageURL()"
Any assistance is much appreciated.
Version: London
Authentication: Central Authentication System (CAS) which uses SAML
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2019 09:01 AM
Thank you for your reply. The answer was actually pretty simple.
Because everything was correct on the back end per several articles on this forum, and docs.servicenow.com I focused on the Login Button in the header.
This is JS I ended up with that provided the desired outcome (returning the user to the page where they logged in as opposed to the Service Portal homepage)
var c = this;
$scope.openLogin = function () {
if (!c.data.is_logged_in) {
c.server.get({
action: "set_sso_destination",
pageURI: $window.location.href
}).then(function() {
window.location = "/login_with_sso.do";
});

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2019 12:41 PM
Hi,
Look at login rules and Installation Exists. you can place your code anywhere for redirection in these 2 place as they both execute after login.
Ref: https://community.servicenow.com/community?id=community_blog&sys_id=0a3daae5dbd0dbc01dcaf3231f9619fa
Mark the comment as a correct answer and helpful once worked.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2019 09:01 AM
Thank you for your reply. The answer was actually pretty simple.
Because everything was correct on the back end per several articles on this forum, and docs.servicenow.com I focused on the Login Button in the header.
This is JS I ended up with that provided the desired outcome (returning the user to the page where they logged in as opposed to the Service Portal homepage)
var c = this;
$scope.openLogin = function () {
if (!c.data.is_logged_in) {
c.server.get({
action: "set_sso_destination",
pageURI: $window.location.href
}).then(function() {
window.location = "/login_with_sso.do";
});

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2019 10:39 AM
Great, it helps.
Kindly mark the comment as helpful if it has helped you to solve the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2021 01:12 PM
But login rules do not affect the service portal.