Login screen for access to ESC portal - non fulfillment user

terrieb
Tera Guru

So we just upgraded to Xanadu on our production instance and today our Service Desk Manager is insisting that upgrade "broke" how people without a role login to the employee portal.  There is now an option to click on "use external login" that takes extra steps for them to login.  However, if they use the default screen to login, once they input their username and password, it takes them to the portal.

 

I am at a loss as to how to "fix" this as I looked in the Content Management module and nothing has changed since 2009....

 

Attaching screen shots - he reported this as an Incident and upgraded it to a P1 status...

 

Thank you

5 REPLIES 5

Ankur Bawiskar
Tera Patron
Tera Patron

@terrieb 

How was it looking earlier?

which link they are using to login?

If they use the link which has esc portal suffix then that's the OOB login page.

Nothing has changed in Xanadu. The below screenshot is from Washington DC.

AnkurBawiskar_0-1737553103925.png

 

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

Is there a way to remove the "use external login" option on this screen?

 

terrieb_0-1737553648295.png

Thank you

 

 

@terrieb 

I am not seeing that in Xanadu instance

When they click that Use external login is it taking them to SSO page?

check this link

how to remove external login link in login page? 

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

I got the solution from Support

 

It turns out we were missing a glide record for the SSO ver 2.

 

Now it's back to autologin if the person is accessing the portal from onsite or offsite and on VPN  They will only be prompted now if they are offsite and not using VPN, which is the way they should be.  Okta verification will then be required...

 

Thanks for your response