Hi Heikki, Thank you very much. That clarifies things and seems to have been the missing link. :-)
With kind regards Stefan On Wed, 18 Dec 2024 at 14:38, Heikki Vatiainen via radiator < [email protected]> wrote: > On 18.12.2024 11.50, Stefan Paetow (OpenSource) via radiator wrote: > > > Thank you for clarification! Also, does using 'Asynchronous' make sure > > that AuthBy RADSEC gets executed first (and waits for a response) before > > falling back to AuthBy RADIUS? The documentation implies so. > > Yes, 'Asynchronous' is the easiest option for this. With this option the > AuthBy works similar to the AuthBys, such as SQL and LDAP, which return > IGNORE when they can't get a meaningful response from the DB or directory. > > Something like this should do it: > > <Handler ...> > # This is the default policy, here as a reminder > AuthByPolicy ContinueWhileIgnore > > <AuthBy RADSEC> > # Parameters > Asynchronous > # More parameters > <AuthBy RADSEC> > > <AuthBy RADIUS> > # Parameters > Asynchronous > # More parameters > </AuthBy> > > # More parameters > </Handler> > > You can use Status-Server or timeout based alive detection as usual with > the above clauses. For example: > > > https://files.radiatorsoftware.com/radiator/ref/AuthByRADSEC.html#Host_AuthByRADSEC-7 > > Thanks, > Heikki > > -- > Heikki Vatiainen > Radiator Software, makers of Radiator > Visit radiatorsoftware.com for Radiator AAA server software > > > > _______________________________________________ > radiator mailing list > [email protected] > https://lists.open.com.au/mailman/listinfo/radiator >
_______________________________________________ radiator mailing list [email protected] https://lists.open.com.au/mailman/listinfo/radiator
