[RADIATOR] Handler Match on Secret?

[Hugh Irvine]

Hello Cassidy -

I’m not sure I  understand the requirement - if you don’t have a Client device listed, Radiator will ignore any RADIUS requests coming from it.

The usual way to do this sort of thing is with Identifier’s in the Client clauses, with Handler’s to match.

Maybe give us a bit more detail on what you want to accomplish?

regards

Hugh

> On 27 Aug 2019, at 06:27, Cassidy B. Larson <alandaluz at gmail.com> wrote:
> 
> Is there a way to do a Handler match based on the Secret?
> 
> We have a number of different devices that I'd like to segregate into separate Handlers based on their Secret.   I'd rather not have to update the ClientListSQL database each time I add a new one. 
> 
> Any thoughts?
> 
> Thanks!
> 
> -c
> _______________________________________________
> radiator mailing list
> radiator at lists.open.com.au
> https://lists.open.com.au/mailman/listinfo/radiator


--

Hugh Irvine
hugh at open.com.au

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER, SIM, etc. 
Full source on Unix, Linux, Windows, macOS, Solaris, VMS, NetWare etc.