Which authentication flow is being used?

Question

Which authentication flow is being used?

ffried opened this issue 3 years ago · 9 comments

I've set up this plugin in our Keycloak instance, but I can't figure out which Authentication Flow is being used.

Background is, that our users are required to have an OTP setup, but the OTP is only necessary for the certain flows (mainly the Browser flow). Other flows still allow usage of the OTP but do not require it, since logins with these flows is restricted to certain clients and users.
With this radius plugin, I'm able to log in using the password plus OTP, but am not able to log in using only the password.

Is there a way to tell this plugin to use a separate authentication flow which only requires the password and optionally takes the OTP?

Answer 1 · 2021-12-06T13:26:52.000Z

Hi @ffried ,
Radius at self does not support any flow.
Radius is a networking protocol that provides centralized authentication, authorization, and accounting (AAA):
Keycloak-Radius-plugin map RADIUS protocol to Keycloak Client Protocol :
(A)uthentication - Keycloak authentication including federated users and OTP
(A)uthorization - Keycloak Role/Group/Resources
(A)ccounting - Keycloak session.

The Otp password is required for Radius only in two cases:

if the user is assigned "Configure OTP"
The user has already configured OTP

For authentication without OTP for a specific user or users, simply remove "Configure OTP" from the required actions.

Answer 2 · 2021-12-06T13:30:48.000Z

If you enable the "Default Action" for "Configure OTP", then all new users will be assigned the required "Configure OTP" action.

Answer 3 · 2021-12-06T14:23:15.000Z

That's exactly the issue. I'd like to allow users to login without otp when using RADIUS. In Keycloak I can configure this using the authentication flows.

For example, we'd like to use this as our RADIUS backend for the internal WiFi. We'd like our users to login with their credentials (similar to our other services) but not have to provide their OTP.

Answer 4 · 2021-12-06T16:40:15.000Z

I think for your use case you can use another solution:

You have WiFi radius hotspot with html page.

Instead of using direct authentication using radius credential you can use authentication in two steps.

Authenticate user on your hotspot page using openid protocol. Here you can use keycloak browser flow to authenticate as you want, for example if your organization use identity provider like Google, Okta etc.. then you can configure it for this page. Result of this authentication you will receive signed JWT token with temporally(or onetime) radius password.
authenticate to radius server using credentials from the JWT token

How add credentials to JWT : https://github.com/vzakharchenko/mikrotik-hotspot-oauth#setup-build-and-configure--hotspot-page-for-social-login

Here two type of temporally radius password "Onetime Radius Password" and "Session Radius Password":

Onetime Radius Password - you can use password only once during user session. For a new password, you need to issue a new JWT.
Session Radius Password - you can use multiple time the same password until session is alive

examples:
https://github.com/vzakharchenko/keycloak-radius-plugin/wiki/WebAuthnRadius#get-radius-password-from-code
https://github.com/vzakharchenko/keycloak-radius-plugin/wiki/WebAuthnRadius#nodejs-example-for-getting-temporary-radius-password

Answer 5 · 2021-12-06T17:01:45.000Z

I'm afraid that won't work.
WiFi is only one use case. The other one is our VPN. Also, we will provide the WiFi (and VPN) configuration via MDM (only password is missing). So our users should only input their password and then connect.

Answer 6 · 2021-12-08T08:19:11.000Z

@ffried, https://github.com/vzakharchenko/keycloak-radius-plugin/wiki/RadiusOTP

Answer 7 · 2021-12-08T10:40:49.000Z

@vzakharchenko Thank you for adding this!!!

However, I'm unable to get this switch to show up...
We're deploying Keycloak using docker-compose. I've recreated the container after I've updated the (docker) scripts with those from master. I see that the script now downloads version 1.3.14 of the artifacts.
Next, I've verified that inside the container the zip in /opt/jboss/keycloak/modules/keycloak/plugins/radius/theme/main matches the one I've downloaded directly (md5 of the zips match: a66d507ce521b7a7927c72e3dcfee436).

I've switched from and to the radius theme (including logouts in between and even restarting the keycloak container in between) but this new toggle doesn't show up.
We're using a separate realm (not Master). I've tried using the theme in both realms and even tried to create a radius client in Master. No luck.

There is a weird glitch if I enable the radius theme in our realm but not in the master realm. Then after a logout and a login the client edit page looks like this:

Do you have an idea what might go wrong here? How can I get the toggle to show up?

Answer 8 · 2021-12-08T20:29:17.000Z

@ffried , Looks like deployment issue.

I redeployed docker images, please clear local docker cache.

The simplest way is to change the admin theme for the ** "master" ** realm, because master realm has cross-realm access.

But If you want to use radius theme for the specific realm then you need:

create admin user and assign to him all admins roles from realm-managment client:
open admin console page for your realm: http://localhost:8090/auth/realms/<RADIUS_REALM>/protocol/openid-connect/auth?client_id=security-admin-console&redirect_uri=http://localhost:8090/auth/admin/<RADIUS_REALM>/console&response_mode=fragment&response_type=code&scope=openid where RADIUS_REALM - your realm name.
To login use credentials from step 1.

Answer 9 · 2021-12-09T13:26:09.000Z

Still couldn't get the toggle to show up. But I've used the kcadm.sh script inside the container now to set the radius.OTP attribute of the client to false. Works great now!

This is proof that the deployment worked. Seems like something is weird with the theme, but I have no idea what this could be. Even tried turning off theme caching in keycloak.