Force OKTA Log In on a specific Service Portal page.

[Sean Burton]

So we have SSO log ins for our home Service Portal page using OKTA.

The issue I am having is a scenario where we send a URL in a notification to specific internal users for a specific Service Portal page. For users to use this hyperlink, they have to first log in to the main page, then they can click the link.  I really need users to be able to click the link, login, then direct to the specific Service Portal page. 

I tried adding the sso login to the hyperlink, 

https://assurant.service-now.com/sip/login_with_sso.doglide_sso_id=b631b5e8dbdea30008fc808768961982

The problem with this is once you login, it redirects the user to the standard landing, https://assurant.service-now.com.

Does anyone know the right method to force okta sign ons for a specific URL? 

[Kieran Anson]

Hi,

The login_with_sso method doesn't support deeplinking. Is Okta your only login mechanism? Can you enable IdP auto-redirect?

If not, you'll need to modify the login page for the /sip/ portal to either auto-redirect to Okta or offer an option to initiate the redirect to the Okta login page.

You can look at the widget-login that shows:

• Using new GlideSPUtil().getPageUri(); to get the page the user navigated to (and the page we want to return them too post login)
• Storing this value in "nav_to" to redirect the user upon return to ServiceNow

[Tuan Vu]

Hi, to redirect the user to a specific page after SSO, you need to do the following steps.
1. Open the settings on Okta application, set "Default Relay State" attribute to be your specific portal URL
2. on Servicenow, navigate to the system property table and create the property below
glide.authenticate.honor.relaystate.for.loggedin.sessions 
Type: true|false 
Value: true