Service Portal SSO login does not redirect users back to Service PortalIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When users access the Service Portal and then log in via SSO, the expectation is that they will be taken back to the Service Portal, however they are instead taken to the platform view (navpage.do) or an asset (font, image, etc). Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Cause #1 - Applies to all versions Cause #2 - Applies to Paris and later Cause #3 - Applies to all versions Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Cause #1 - An asset (image, font, etc) used within the Service Portal is non-public Within your browser (Chrome or Firefox), open Developer Tools and then Network tab (ensure you check Preserve Log).Navigate to your Service Portal (https://acme.service-now.com/sp).Within the network capture you may observe an asset (ie. "iix" font file, "png/jpg" image file or in this case a "sys_attachment" record) results in a "302 / Redirect".If a user is not authenticated and they attempt to load/view a non-public asset, the instance will force the user to authenticate first (usually SSO). However in this case, the redirect is potentially overriding the SSO redirect from the Service Portal's "Login" widget and so after authentication, users are redirected back to "navpage.do" or the asset in question. Cause #2 - A custom "Login" Widget is used and this behaviour started after upgrading to Paris or later Prior to Paris, the instance will remember the last public page that a user accessed (Service Portal in this case), and so after authentication the instance will know to return the user to that page (Service Portal). However from Paris and onwards, this is behaviour has changed and is no longer the case. Cause #3 - An asset is incorrectly referenced by Angular binding/variable Within your browser (Chrome or Firefox), open Developer Tools and then Network tab (ensure you check Preserve Log).Navigate to your Service Portal (https://acme.service-now.com/sp).Within the network capture you may observe a request to what appears to be an Angular binding expression but not replaced correctly with its substitution value which results in a "302 / Redirect".Because the user is unauthenticated, the session does not allow access to what is truely behind the URL (assuming it's not public) then it requires authentication, which in turn will override the Relay State (similar to cause #1). Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Resolution #1 - An asset used within the Service Portal is non-public The asset (font, image, etc) will need to be removed or made publicly accessible. Please refer to the below links for assistance: Product Documentation - Storing images in the databaseKB0782047 - From the Service Portal login page, use of custom fonts causes login button to attempt to download the custom fontNOW Community - Using Custom Fonts In Service Portal Resolution #2 - A custom "Login" Widget is used and this behaviour started after upgrading to Paris or later Please revert to using the OOB "Login" Widget within your Service Portal.If there is a requirement to implement a custom login widget, within the "Server script" you can set the GlideSession property "starting_page" to define the relay state (the page accessed after login). gs.getSession().putProperty("is_direct_redirect", "true"); gs.getSession().putProperty("starting_page", "/sp"); Resolution #3 - An asset is incorrectly referenced by Angular binding/variable The most common origin of this issue is within Service Portal Themes, where Angular binding expression is referenced with the "src" attribute: <img src="{{::portal.logo}}" title="{{::portal.title}}" alt="{{::portal.title}} ${Logo}" /> The correct correct attribute should be "ng-src" when using Angular binding expressions. <img ng-src="{{::portal.logo}}" title="{{::portal.title}}" alt="{{::portal.title}} ${Logo}" />