* website/docs: clear up radius provider Signed-off-by: Jens Langhammer <jens@goauthentik.io> * Update website/docs/providers/radius/index.md Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com> Signed-off-by: Jens L. <jens@beryju.org> Signed-off-by: Jens Langhammer <jens@goauthentik.io> --------- Signed-off-by: Jens Langhammer <jens@goauthentik.io> Signed-off-by: Jens L. <jens@beryju.org> Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com>
1.6 KiB
title |
---|
Radius Provider |
:::info This feature is still in technical preview, so please report any Bugs you run into on GitHub :::
You can configure a Radius Provider for applications that don't support any other protocols or require Radius.
:::info This provider requires the deployment of the RADIUS Outpost :::
Currently, only authentication requests are supported.
Authentication flow
Authentication requests against the Radius Server use a flow in the background. This allows you to use the same policies and flows as you do for web-based logins.
The following stages are supported:
-
Note: Authenticator validation currently only supports DUO, TOTP and static authenticators.
For code-based authenticators, the code must be given as part of the bind password, separated by a semicolon. For example for the password
example-password
and the code123456
, the input must beexample-password;123456
.SMS-based authenticators are not supported as they require a code to be sent from authentik, which is not possible during the bind.
Limitations
The RADIUS provider only supports the PAP (Password Authentication Protocol) protocol: