Hello Christian -
I am not suggesting another AuthBy FILE - you can do the same thing in RADMIN. The example was simply to show you how Radiator works with multiple DEFAULT, DEFAULT1, DEFAULT2, etc. regards Hugh > On 20 Jan 2019, at 21:14, Christian Meutes <christ...@errxtx.net> wrote: > > Hey Hugh, > > On Sun, Jan 20, 2019 at 2:30 AM Hugh Irvine <h...@open.com.au> wrote: >> DEFAULT User-Name = /hugh/ >> Reply-Message = DEFAULT >> >> DEFAULT1 User-Name = /christian/ >> Reply-Message = DEFAULT1 > > I'm not able to see how indroducing another 'AuthBy FILE' can help me > with my logic, apologies. > I do understand how to use a user file with DEFAULT and further > check-items. But I think I really need to use this inside of RADMIN, > because having another 'AuthBy FILE' right after RADMIN would mean not > being able to differentiate anymore between "user not found and user > found and accepted (AcceptIfMissing)" or "user not found and user > rejected (default logic)". In the former case (user found and > accepted) it would still consult LDAP. In the latter case it would not > consult LDAP anymore. > > Thanks / Best regards > -- > Christian -- Hugh Irvine h...@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. _______________________________________________ radiator mailing list radiator@lists.open.com.au https://lists.open.com.au/mailman/listinfo/radiator
