Global Protect portal authentication with LDAP fails

[usvi]

We have set up GP to authenticate against an AD server . User group mapping has done and u can pull the users . However, whenever you try to connect with one of the  users from the GP client or portal web page ,  you get authentication  fails message . Connecting with local db works fine . Any ideas ? I saw an article about spaces in the authentication profile . The profile has no space it is called localAD.

[gafrol]

Hi,

I don't know what the problem with LDAP against AD could be in your case, but for the same purpose I am using a Kerberos Server Profile and a Kerberos Authentiction Profile in order to authenticate GP users against our MS AD. It looks like this

Maybe you can give it a try ?

Roland

[usvi]

Hello,

Upgraded the client to 1.2.1 now localdb doesn't work . I do get the cert error and allow it to import it

[usvi]

Did that and still doesnt work

[gafrol]

Take small steps. Does localdb authentication work again ?

[usvi]

Yes . It does . I had to downgrade to 1.1.6 and use the original cert that was created when the box was deployed . Now I connect using local db , still no AD nor Kerberos connectivity

[gafrol]

Which PANOS is running on your box ?

[usvi · Accepted solution]

4.1.8 .  Had to call TAC and they got to work . DN binding was incorrect and we missed the samaccountname under ldap authentication  profile .

[gafrol]

That's why I'm using Kerberos for authentication, it's much easier no fiddling around with bindings and samaccountnames etc.

[usvi]

I guess , we shall use Kerberos on other deployments