ADFS SAML Configuration

[benjaminsutter]

Hi all

I need help to configure ADFS SAML with global-protect.

i have successfully imported the metadata.xml from adfs into palo.

But now i can't export the metadata from paloalto. 

Whats the correct identifiers and endpoints urls for global-contect clientless? I have no idea, what i must configure in adfs. 

Can anyone help?

I use panos 8.0

regards

Benjamin

[rcknight]

I just recently was able to get GP to authenticate to ADFS using SAML with the help of support.  Here are some hints that worked for me.

1. GP 4.0.3 has a bug, so I needed to use either GP 4.0.2 or GP 4.0.4

2. ADFS is configured with a Custom Claim Rule, a Transform rule to map SessionID to NameID (using transient identifier) and another Transform rule to map Windows Account Name to username

3. username is used for Username Attribute in the SAML auth profile

Let me know if that helps you.

Ian

[chrkli193]

Hi,

can you add a screenshot of your rules?

Thanks

[chrkli193]

After a lot of trying I'm at the point that I can login via SAML to global protect. I'm using three rules in ADFS configuration:

1. Rule:

c1:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname"]
 && c2:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/authenticationinstant"]
 => add(store = "_OpaqueIdStore", types = ("http://mycompany/internal/sessionid"), query = "{0};{1};{2};{3};{4}", param = "useEntropy", param = c1.Value, param = c1.OriginalIssuer, param = "", param = c2.Value);

2. Rule:

3. Rule:

I use sAMAccountName instead of username in my Authentication Profile.

For just logon to global protect via SAML that seems ok. 

But I want to use Clientless VPN with apps that also do a SAML authentication. At the moment the situation is the following:

I open the global protect portal and get redirected to the ADFS logon site (external Form authentication). I logon and get redirected to the Clientless VPN portal.

Then I click on one app which also uses SAML authentication. I expect that the app will just open because I'm already authenticated via SAML BUT I get another ADFS authentication window (internal Windows Authentication) and have to logon again. 

When I then open another app from clientless vpn portal then this works via SSO.

I think that happens because ADFS cannot map my session after I'm authenticated to the global protect portal so I think there is still missing something in the configuration of the rules.

(Another information: I had to delete encryption and signature info in ADFS for the Clientless VPN party. I don't know why but I will check this later.

)

Any ideas?

Thanks!

[rcknight]

I'm sorry, but I don't have any ideas for use with clientless vpn.  I've only been focusing on GP.  Right now I'm working through issues with the signing certificate verification and the signing of SAML requests to the iDP.  Maybe my eventual findings here might help you with your last comment.

[chrkli193]

But can you add screenshots of your ADFS rules?

Thanks!