Deeplinking Issues

[vcaracci75]

We currently have SSO enabled via F5. I created a link to allow users to go directly to one of our requested items directly from a link in our intranet. Because this SSO is SP-initiated, "deep-linking" should work by default. Our F5 access policy is configured to allow this feature, so there could be something in the ServiceNow config that needs to be enabled/configured for this to work. Right now the links only work if you have an active session.If you don't have an active session established, You will either get directed to our ESS page, or the login page. I spoke with ServiceNow tech support and their solution was to make the page in question public. Given the obvious security issues associated with that, we do not see that as a viable solution. Has any one else run into this, and if so, how did you correct it?

Thanks!

[tltoulson]

<instance_name>.service-now.com/navpage.do?uri=com.glideapp.servicecatalog_cat_item_view.do?v=1&sysparm_id=c2f2eacf138b92008fcdf3b12244b0b2&sysparm_link_parent=ce35e2c513bf5600f0cbbda12244b052&sysparm_catalog=e0d08b13c3330100c8b837659bba8fb4&sysparm_catalog_view=catalog_default

A couple problems you may run into:

1.   You may need to URL encode the second "?" to "%3F" and the "&" to "%26"

2.   ServiceNow's redirector page used to have a bug where it would only accept 1 url parameter in the query string.   Basically it would chop off anything after the first ampersand.   If that is still an issue, let me know.   I have something floating around the community I can try to dig back out to fix it.

[vcaracci75]

Sorry, this is what I used: https://