Wireless Access

last person joined: 21 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Captive Portal LDAP authentication failed

This thread has been viewed 5 times

  • 1.  Captive Portal LDAP authentication failed

    Posted Oct 08, 2020 01:05 AM

    Hello, im trying to set up a captive portal authentication with LDAP server on an Aruba Controller. I successfully integrated the controller with the LDAP server, as seen in the AAA diagnostics test:

    Pokekman_0-1602133383607.png

    But when i connected to the SSID and tried to log into the captive portal, it shows authentication failed.

    This is what i found from the log:

    Oct 8 10:29:38 :133019:  <3560> <ERRS> |localdb|  User wifi was not found in the database
Oct 8 10:29:38 :133006:  <3560> <ERRS> |localdb|  User wifi Failed Authentication (Processing USER_REQUEST on UserDB)
Oct 8 10:29:38 :133121:  <3560> <WARN> |localdb|  make_response: Sending USERDB_REJ-msg to 127.0.0.1:8214 with msgtype:23 id:55 reqtype:1 dbtype:0
Oct 8 10:29:50 :133019:  <3560> <ERRS> |localdb|  User direksi1 was not found in the database
Oct 8 10:29:50 :133006:  <3560> <ERRS> |localdb|  User direksi1 Failed Authentication (Processing USER_REQUEST on UserDB)

    Is there any configuration that i should do? 

    Thank you.



  • 2.  RE: Captive Portal LDAP authentication failed

    MVP GURU
    Posted Oct 08, 2020 06:52 AM

    Have you added the LDAP server correctly?

    https://community.arubanetworks.com/t5/Controller-Based-WLANs/How-do-I-configure-LDAP-on-the-Aruba-controller/ta-p/184056


    Also have you added the LDAP server in the AAA profile?

     

     



  • 3.  RE: Captive Portal LDAP authentication failed

    Posted Oct 08, 2020 07:03 AM

    Yes, i also followed that guide 

    I have added the ldap server to the AAA profile



  • 4.  RE: Captive Portal LDAP authentication failed

    MVP GURU
    Posted Oct 08, 2020 07:06 AM

    And you checked this step?

    4) Enable the termination in the controller with eap-peap and eap type as eap-gtc and no machine authentication as for now

     

     

     



  • 5.  RE: Captive Portal LDAP authentication failed
    Best Answer

    EMPLOYEE
    Posted Oct 08, 2020 09:22 AM
    @Pokekman wrote:

    Hello, im trying to set up a captive portal authentication with LDAP server on an Aruba Controller. I successfully integrated the controller with the LDAP server, as seen in the AAA diagnostics test:

    Pokekman_0-1602133383607.png

    But when i connected to the SSID and tried to log into the captive portal, it shows authentication failed.

    This is what i found from the log:

    Oct 8 10:29:38 :133019:  <3560> <ERRS> |localdb|  User wifi was not found in the database
Oct 8 10:29:38 :133006:  <3560> <ERRS> |localdb|  User wifi Failed Authentication (Processing USER_REQUEST on UserDB)
Oct 8 10:29:38 :133121:  <3560> <WARN> |localdb|  make_response: Sending USERDB_REJ-msg to 127.0.0.1:8214 with msgtype:23 id:55 reqtype:1 dbtype:0
Oct 8 10:29:50 :133019:  <3560> <ERRS> |localdb|  User direksi1 was not found in the database
Oct 8 10:29:50 :133006:  <3560> <ERRS> |localdb|  User direksi1 Failed Authentication (Processing USER_REQUEST on UserDB)

    Is there any configuration that i should do? 

    Thank you.

    This means that your Captive Portal Authentication Profile server group is "default" which is pointing at the local database.  You need to create a server group that includes your LDAP server and then change your Captive Portal authentication profile to reference that server group so that it is authenticating to your LDAP server.

     

    To be clear, the server (group) that is queried for Captive Portal is in the Captive Portal Authentication profile, NOT the AAA profile.  All the AAA profile does is put the user in the Initial user role, whose ACLs trigger a Captive Portal.  The Captive Portal Authentication Profile referenced in that initial user role is what decides the user store that is queried by the Captive Portal.