Hello -
I am working on configuring a captive portal setup for our network.
I find that when I assign the Radius servers as the authentication method for the captive portal authentication keeps failing. Looking at my Radius logs, I find this:
------------
Authentication Details:
Proxy Policy Name: Use Windows authentication for all users
Network Policy Name: FacStaff Dot1x Wireless (Offices Net)
Authentication Provider: Windows
Authentication Server: sturgeon.evergreen.edu
Authentication Type: PAP
EAP Type: -
Account Session Identifier: -
Reason Code: 66
Reason: The user attempted to use an authentication method that is not enabled on the matching network policy.
------------
However, I can log in just fine to the management web ui, using the exact same AAA profiles / servers. When I review the logs for my login on the management ui, it shows this:
-----------
Authentication Details:
Proxy Policy Name: Use Windows authentication for all users
Network Policy Name: FacStaff Dot1x Wireless (Offices Net)
Authentication Provider: Windows
Authentication Server: sturgeon.evergreen.edu
Authentication Type: PEAP
EAP Type: Microsoft: Secured password (EAP-MSCHAP v2)
Account Session Identifier: -
-----------
Is this by design? Or am I missing something? I understand that normally PEAP would be used to encapsulate the request and pass it through to the radius server, but if the Web UI is able to that, why can't the captive portal? Or perhaps the question is why *won't* the captive portal?