Captive Portal with LDAP

[johnd]

Hi,

I've read all the guides and on the forums and still can't figure out why my configuration won't work.

I want users to enter AD username/password to get access to the internet.

The following has been configured:

Device > User Identification > Group Mapping Settings:

1. Added server profile

2. Rest is default

3. Group Include List, entered AD and located my security group i want. (So LDAP connection is working).

Also, when running "Show user user-ID's", both the users in the group are listed, so they are being read.

Device > User Identification > Captive Portal Settings:

1. Enabled captive portal

2. Authentication Profile is correct.

3. Mode redirect (Clients can see the webportal, so this is working)

Network > Zones > Trust:

1. Enabled User Identification.

Device > LDAP:

This is obviously working or else i wouldnt have a connection (?).

Device > Authentication Profile:

1. Allow list is set to all.

2. Authentication set to LDAP.

3. Login attribute set to sAMAccountName

When testing this on a client i get the following:

Captive Portal authentication failed for user: X on 192.168.X.X, vsys1

User 'X' failed authentication. Reason: Invalid username/password from: 192.168.X.X.

Any clues?  I'm not using user-identification agent, this shouldnt be needed as i have LDAP and when using local users the authentication worked fine!

[rmonvon]

Did you try entering username & password, or domain\username & password?

[johnd]

I tried both in all variations. Also reset my domain password to be sure.

As i said it worked just fine with local user accounts.  And AD seems to be working just fine, so I'm not sure what the problem is.

Does anyone know which debugging option i should enable to see whats wrong.  Guess i could do some packet capture as well.

[rmonvon]

You can test the LDAP config by setting it to authenticate the admins.  Then use your LDAP username/password to login as an admin for the PA device.

[johnd]

Well, that didnt work either.

tail mp-log authd.log

Dec 22 12:41:31 pan_authd_common_authenticate(pan_authd.c:1520): Authenticating user using service /etc/pam.d/pan_ldap_vsys1_:domain :users_1,username XX_USER_XX failed - trying other hosts
Dec 22 12:41:31 pan_authd_common_authenticate(pan_authd.c:1495): Skipping LDAP server due to missing Auth-Profile: pan_ldap_vsys1_:domain :users_2
Dec 22 12:41:31 pan_authd_common_authenticate(pan_authd.c:1495): Skipping LDAP server due to missing Auth-Profile: pan_ldap_vsys1_:domain :users_3
Dec 22 12:41:31 authentication failed for user <vsys1,Domain Users,XX_USER_XX>
Dec 22 12:41:31 pan_authd_process_authresult(pan_authd.c:1247): pan_authd_process_authresult: XX_USER_XX authresult not auth'ed
Dec 22 12:41:31 pan_authd_process_authresult(pan_authd.c:1271): Alarm generation set to: False.
Dec 22 12:41:31 User 'XX_USER_XX' failed authentication.  Reason: Invalid username/password From: 192.168.0.15.
Dec 22 12:41:31 pan_get_system_cmd_output(pan_cfg_utils.c:3019): executing: /usr/local/bin/sdb -n -r cfg.operational-mode
Dec 22 12:41:31 pan_authd_generate_system_log(pan_authd.c:833): CC Enabled=False
Dec 22 12:41:31 pan_get_system_cmd_output(pan_cfg_utils.c:3019): executing: /usr/local/bin/sdb -n -r cfg.operational-mode

[rmonvon]

A couple of things to check.

Check the log of your LDAP server and is it reporting incorrect  credential as well?  If so, have you try a different account, username/password?

Are you seeing LDAP groups if you issue CLI command: show user ldap-server server <name>

If there's no groups listed in the output, then the LDAP config is incorrect.

You may also want to contact Support and have your configruation reviewed over a web meeting.  Thansks.

[johnd]

I can browse the AD directory from the PaloAlto, also in CLI the FW is showing the users in the group i've selected.

However, when trying to authenticate users it seems like the FW can't reach the LDAP server.  I have 1 rule and it allows all!!

I can also ping from all the network interfaces on the firewall!

[rmonvon]

As the next step, I would suggest contacting Support and have it diagnose.  Thanks.

[johnd · Accepted solution]

This was solved by removing all the LDAP config and Captive Portal config and adding it all again.

Seemed to be some bug with the config.

[rmonvon]

Glad to hear that it worked.   Cheers.