Service Portal SSO login does not redirect users back to Service PortalIssue 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). ReleaseCause #1 - Applies to all versions Cause #2 - Applies to Paris and laterCauseCause #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. ResolutionResolution #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");