How do you allow access to service portal from url without signing in?

[thoma5]

So when the user tries to access a portal from the direct URL by entering it in the browser navigation bar, they are brought to a log in page and are prompted to sign in even though they may have already been signed in.

I notice that this happens if this is the first time the user tries to access the portal directly from the URL or if they haven't done so in a while. However if the user accesses the portal from a link inside of ServiceNow, this does not happen.

Currently if I get to a log in page, delete the ".com/portalName" part of the URL, press enter, the page refreshes and then loads into the portal page without the user actually signing in.

Is there any property I can change to fix this?

Thanks!

[Allen Andreas]

You could make the page public, which turns off the need to login, but I think you're speaking about two different things here. The login page only appears if SN needs them to login and the cache/cookie or whatever is wiped/times out.

https://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/administer/general/task/t_MakeAP...

[thoma5]

Hi Allen,

Yeah I just read about making pages public right before your post haha

But I guess I don't fully understand what's going on either. So coming off this statement "The login page only appears if SN needs them to login and the cache/cookie or whatever is wiped/times out."

Let's say the user is logged in to SN but instead of going to the portal from a link in SN, they enter it in the URL, and sees the login page, is this caused by the lack of existing cache/cookie?

Is there a way to fix it or will the work around be to just delete the second half of the URL and let it reload/save the cache/cookie for next time?

[Allen Andreas]

Check this: https://docs.servicenow.com/bundle/geneva-servicenow-platform/page/administer/user_sessions/task/t_M...

They must not be an everyday user?

[thoma5]

OOh this seems like it will be helpful in the future. Thank you!

But yeah, we are currently seeing this when users are trying to access a new portal we just rolled out for the first time. I have a requirement to remove the need for them to log in again given that they are coming from SN but have entered a direct URL instead of clicking the internal link.

I guess the best work around would be to get them to access it from SN first..? Or let them know to delete the trailing url and that it should automatically refresh the page.