-
Notifications
You must be signed in to change notification settings - Fork 48
mikrotik login radius, does not find or does not authenticate user login winbox. #659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I just solved it by doing a fresh install the problem may be involved in the radius authentication issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My settings are these:
° keycloak radius plugin installed quarks. (ubuntu 20.04.3) ( external server )
running: /opt/keycloak-radius# bin/kc.sh start --hostname=mydomain.cloud --hostname-strict-backchannel=true --https-port=8443
° configured https tls and hostname external ip ( no proxy ).
° radius over TLS configured as radsec port 1812 ,1813.
° configured "mikrotik-radius-plugin" only for login mikrotik
° user created for login test
My Mikrotik
° Routerboard RB750GR3 version 6.49.6 (stable)
° configured radius radsec, accouting AAA
The mistake:

when i go to login by winbox i get the following error in keycloak terminal.
STATUS RADIUS ROUTERBOARD
I don't know where I'm going wrong.
The text was updated successfully, but these errors were encountered: