Prisma Access - CIE multi profile - breaks SSO

[gcollins5]

Hello all . 

Seem to be casting into an empty pool here but will try anyway. 

My issue is with Multi Auth profiles using Global Protect & Prisma Access. 

If you use more than one IDP you can only match against one profile , hence you can't use multi profile. 

So recommended is CIE multi Auth .

You setup your IDPs in here , easy peasy  and it works. 

Only problem is when  you authenticate against  the CIE multi Auth . 

You get a new PAlo Alto landing page which requires you to enter your user ID so CIE can work out which IDP to point you towards. 

This breaks SSO completely . SO , if like me you allow Windows authentication FIRST  before GP starts , CIE does not use the already granted token because it does not know which directory to point it at , hence you have to enter a users name,, it then is able to see the token is valid and  authentication is satisfied and we move on .

Pretty dumb as is completely break SSO . The only option is to move from a working fully integrated IDP to one where users have to enter their user ID.

TAC tells me this is expected behaviour . I can't believe this is actually true as it makes no sense at all to break SSO . 

As usual there is no documentation (or I cant find it) on how to configure Mutli Auth profiles to cater for this limitation. 

There might be some Kung Fu in global protect thats allows it ?

Anyone else seen this ?????

HELP !!!

[gcollins5]

BUMP !!!!

[gcollins5]

Hello Elizabeth32. 

Finally got some traction on it . My SE Rob has been excellent. 

It is expected behaviour. Ergo  SSO gets broken on purpose. 

The reasoning on this seem to be that CIE cannot interpret the token . So the defined method is to add a proxy type layer where the users inserts their username into a  landing page and CIE directs accordingly . 

The workaround is to use the default browser on the endpoint and create a dummy record  in the password management  of the browser for the  CIE landing page, this automatically completes the users input but there is still a  submit button . 

It is a work around for now but it still breaks SSO . 

My SE setup a meeting with the IAM guru for Europe and we went through the scenario , it is a  weaknesses which is well recognised by Palo . 

Seems the best way is to be able to assign an authentication profile to the Global Protect policy which takes away the need to  have that proxy landing page  and does away with the multi profile CIE policy .

They have actually put. a change request in for this or something similar. 

Very positive input from Palo . Just a huge shame TAC were not aware of how this works and took ages to try and diagnose.