[RADIATOR] Copying OSC-Client-Identifier to Client-Identifier
Tuure Vartiainen
vartiait at open.com.au
Wed Dec 20 11:35:44 UTC 2017
Hi,
> On 20 Dec 2017, at 8.27, Vangelis Kyriakakis <vkyriak at forthnet.gr> wrote:
>
> Is there a way to copy OSC-Client-Identifier which comes from a proxy
> RADIATOR server to Client-Identifier using a PrehandlerHook at the final
> RADIATOR server.
>
Client-Identifier is Radius::Client object’s Identifier attribute’s value,
and is accessible through Radius::Radius request object in a following way
$p->{Client}->{Identifier}
You should not assign a value to it as $p->{Client} is a reference to
Radius::Client object from which the request was received and it would
overwrite that Client’s Identifier’s value.
If you wan’t to unify usage of OSC-Client-Identifier attribute
and local Client-Identifier, you could add Client’s Identifier to
OSC-Client-Identifier attribute if the request does not have one.
E.g.
<Client ...>
Identifier SomeClient
...
# Add Client’s Identifier to OSC-Client-Identifier
# if a request does not have one
AddToRequestIfNotExist OSC-Client-Identifier=%{Client:Identifier}
</Client>
...
<Handler OSC-Client-Identifier=SomeClient>
...
</Handler>
BR
--
Tuure Vartiainen <vartiait 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 etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.
More information about the radiator
mailing list