Using custom login page with SSO implementation

mah1
Kilo Sage

Yokohama Patch 1

 

We are in the process of implementing single sign on. Everything for SSO has been set up/configured and appears to be working as expected.

 

The majority of users will log  in with SSO but there are other users that have local accounts and need to log in with username and password using the standard OOB login page:

mah1_0-1748882627840.png

 

To make things easier for end users,  a custom login page with 2 button options was requested --> button 1 is Sign in with SSO and button 2 is Alternate Login (i.e., for local accounts; this opens /side_door.do).

We created a custom login page for the service portal with that functionality. When users browse to https://<instancename>.service-now.com/sp the custom login page is displayed. The buttons appear to be working as expected with system property glide.entry.page.script set to the default value of new CMSEntryPage().getEntryPage(). 

 

They also want this custom login page to display when a user browses to https://<instancename>.service-now.com

From what I read, this can be accomplished by setting system property glide.entry.page.script to 

new SPEntryPage().getLoginURL() and system property glide.entry.first.page.script to new SPEntryPage().getFirstPageURL() . That seems to provide the requested behavior of using the custom login page when browsing to either https://<instancename>.service-now.com/sp or https://<instancename>.service-now.com

 

However, we are experiencing issues with those property settings. The Alternate Login button doesn't open the standard OOB login page unless you first log in as someone with SSO; it just refreshes the custom login page. Once that is done and you log out, clicking the Alternate Login button opens the standard OOB login page to allow logging in with a local account. Once you log in with a local account and then log out, the Alternate Login button won't work again until you log in/out as someone with SSO.  

 

Also, when a user with no roles signs in, the designated service portal page opens which is expected behavior. However, when a user with roles signs in, their default dashboard should open but instead the following is displayed:

 

mah1_1-1748882705572.png

Is there something else we need to do to get the custom login page to work with SPEntryPage? 

 

Thank you!

2 REPLIES 2

Ankur Bawiskar
Tera Patron
Tera Patron

@mah1 

why not train the users who are using local accounts to use login.do?

I doubt you can achieve your current requirement due to some platform limitations.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Not my decision.  They want the login page to be the same for all users.

 

Thank you