On 09/18/2013 01:14 PM, Heikki Vatiainen wrote:
> Thanks, noted. Also noted Garry's message. Something like
> %{RequestOr:attributename} should be quite straight forward to do and
> understand. However, %{RequestAnd:attributename} requires a bit more.
>
>
> Synatax like this might be a possibility:
>
> mikem User-Password=fred, %{RequestOr:Framed-IP-Address}=1.2.3.4|2.3.4.5
The above should be RequestAnd like this.
mikem User-Password=fred, %{RequestAnd:Framed-IP-Address}=1.2.3.4|2.3.4.5
> Here the request would be accepted if:
> User-Password = fred, and
> Framed-IP-Address = 1.2.3.4, and
> Framed-IP-Address = 2.3.4.5
>
> As another example, the required values (e.g., 1.2.3.4 and 2.3.4.5)
> could come from a multivalued LDAP attribute.
>
> If there are examples how the above would be put in use, please let us know.
--
Heikki Vatiainen <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 etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.
_______________________________________________
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
