Bypass SSO in different Service Portal

guiguille · ‎10-18-2017

Hi all,

I have a requirement to create a new portal in my instance, with a page to access a particular type of ticket. I created a new portal, I created the proper pages, and I set them all as public, and I did the same with the widgets. I thought that by having everything as public I was going to be able to bypass the SSO, but apparently not. Do you guys know where should I add the exception for the SSO to bypass anything that goes to the new service portal I created?

Thanks!

guiguille · ‎12-15-2017

Hey Kevin,

Thanks for reactivating the thread, I totally forgot about it.

The answer we received was that we need the main portal ($sp) also to be public. Doesn't matter if you created a separate portal, $sp must be public. We tried that, and it works. It wasn't a problem for us because we had the following pages and widgets set as private, but I think that it's not a proper solution. What I learnt, never use the primary portal in SP, so you can leave the default one as public and you don't need to do that in the one you are using.

View solution in original post

bernyalvarado · ‎10-18-2017

Hi Guillermo,

Is your portal public?

Please follow/validate with the instructions with the below link (just doing the opposite: making it public )

https://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/build/service-portal/concept/c_R...

Thanks,

Berny

guiguille · ‎10-18-2017

Hey Berny,

Already been there. I tried creating the record in that table with active set as TRUE (My portal's name is ATI, I created $ati and $ATI, just in case I was messing up something with the upper case). With or without those records, I get redirected to the okta login page.

Thanks!

guiguille · ‎10-19-2017

Update, we created a ticket in HI. I'll keep you posted.

kevin_eldridge · ‎12-15-2017

I am interested to know the answer to what HI had to say on this issue.

Kevin Eldridge