mejaz at cyberia.net.sa
Tue Apr 30 09:39:20 UTC 2019
I made sure from the NAS side the secret is same as what I have configured
in Client clause.
Is there any other clue?
Thanks in advance..
From: radiator [mailto:radiator-bounces at lists.open.com.au] On Behalf Of
Sent: Monday, April 29, 2019 8:49 PM
To: radiator at lists.open.com.au
Subject: Re: [RADIATOR] Bad-authenticator
On 29/04/2019 12.38, MEjaz wrote:
> I'm getting a "Bad Authenticator" message using > Radiator. Cisco,
> O/S is Solaris. And with MSSQL database.
> Any idea how to fix this? Any help would be appreciated!
Check that the secret within <Client 22.214.171.124> matches what's
configured on that IP address (RADIUS client). You'll see this error when
the server (Radiator) and client (NAS) shared secrets are not equal.
Note that the shared secret is not for encrypting the whole message.
This is why you see most of the values in clear text in RADIUS requests even
if the secret is not correct.
Heikki Vatiainen <hvn at open.com.au>
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, TACACS+, PAM, Active Directory, EAP,
TLS, TTLS, PEAP, WiMAX, RSA, Vasco, Yubikey, HOTP, TOTP, DIAMETER etc. Full
source on Unix, Windows, MacOSX, Solaris, VMS, etc.
radiator mailing list
radiator at lists.open.com.au
More information about the radiator