[RADIATOR] Reject empty username?

[Hugh Irvine]

Hi Robert -

As an alternative, you could use a Class attribute to store a copy of the username during authentication and return it in the Access-Accept.

Then you would always have the username present in the Class attribute in the subsequent accounting requests.

regards

Hugh


> On 4 Feb 2020, at 03:25, Robert Blayzor <rblayzor.bulk at inoc.net> wrote:
> 
> Would something like this work:
> 
> <Handler Request-Type = Accounting-Request, User-Name = /^.+/>
>   ...
> </Handler>
> #
> <Handler>
>   AccountingHandled
> </Handler>
> 
> 
> 
>> We're getting some clients that are just sending an empty (or no)
>> username attribute. Our database requires a non-null username. Rather
>> than just pump them into the database with some bunk username like
>> "NULL" or "none".... How can we silently ignore these accounting records
>> while sending a ACK back to the NAS so it doesn't keep sending them?
> 
> 
> -- 
> inoc.net!rblayzor
> XMPP: rblayzor.AT.inoc.net
> PGP:  https://pgp.inoc.net/rblayzor/
> _______________________________________________
> 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.