You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the RADIUS outpost on Authentik only supports PAP authentication protocol on RADIUS. Unfortunately, I'm not able to implement RADIUS auth on my network access points with this protocol only avaliable.
Describe the solution you'd like
The additional implementation of things like EAP, EAP-TLS, MSCHAPv2
Describe alternatives you've considered
Not sure if there's any other alternative routes for using RADIUS auth for WPA2/3 enterprise authentication. If anyone else has got any ideas for integrating this with Authentik's RADIUS outpost I'd love to hear it
Additional context
I believe this issue is further discussed here: #5328
The text was updated successfully, but these errors were encountered:
There is an alterative to layeh called toughradius. It implements EAP-MD5 and EAP-MSCHAPV2 authentication, so maybe if Authentik will use this in it's Radius Outpost issue can be resolved.
Any updates on this? I would like to set up WPA-Enterprise in our company, however, having to also set up freeradius and connect it to authentik using LDAP seems a little cumbersome. 😅
Is your feature request related to a problem? Please describe.
Currently the RADIUS outpost on Authentik only supports PAP authentication protocol on RADIUS. Unfortunately, I'm not able to implement RADIUS auth on my network access points with this protocol only avaliable.
Describe the solution you'd like
The additional implementation of things like EAP, EAP-TLS, MSCHAPv2
Describe alternatives you've considered
Not sure if there's any other alternative routes for using RADIUS auth for WPA2/3 enterprise authentication. If anyone else has got any ideas for integrating this with Authentik's RADIUS outpost I'd love to hear it
Additional context
I believe this issue is further discussed here: #5328
The text was updated successfully, but these errors were encountered: