Bypass SSO in different Service Portal

[guiguille]

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 · Accepted solution]

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.

[kevin_eldridge]

Thank you guiguille for the response with the answer from HI regarding this. We will weigh doing this versus your other option or anything we come up with. If I find an alternate solution, I will post it here.

Have a wonderful weekend!

Kevin Eldridge

[mdash]

Hi,

We have multiple portals with SSO and want to bypass for a single portal. Can you share what exactly needs to be done?

Thanks

[guiguille]

Hi mdash, the solution over there should be to leave the sp portal as public, and then set as private the other ones that need SSO, and public the one you need to bypass it.

Hope it helps,

[mdash]

Thanks for quick reply. I will try that out. And do I also need to make nay changes to any widgets/pages?