[RADIATOR] Radiator and NavisRadius USS

[Hugh Irvine]

Hello Rohan -

As far as I can see from the online documentation, NavisRadius uses USS as a session database.

This being the case, I think you would need to set up Radiator to proxy to NavisRadius which in turn would use USS.

Note that Radiator also has its own support for one or more session databases, so I imagine you could replicate what USS does completely within Radiator.

I don't think you would be able to configure Radiator to use USS directly, unless you can find out what API is available (if any).

regards

Hugh


On 2 May 2013, at 02:30, <rohan.henry at cwjamaica.com> wrote:

> The plan is to replace NavisRadius but want to integrate Radiator into the production environment as a test run.
> 
> NavisRadius servers are configured to use a USS (NavisRadius Universal State Server installed on a separate server). I was hoping to get Radiator to use the USS. Eventually we would be using a sessions database.
> 
> Rohan
> 
> On Wed, 1 May 2013 10:13:07 +1000
> Hugh Irvine <hugh at open.com.au> wrote:
>> 
>> Hello Rohan -
>> 
>> Can you tell us exactly how you want Radiator and NavisRadius to operate?
>> 
>> As Heikki says, you probably want to use proxy RADIUS, but which is client and which is server?
>> 
>> regards
>> 
>> Hugh
>> 
>> 
>> On 1 May 2013, at 05:19, Heikki Vatiainen <hvn at open.com.au> wrote:
>> 
>>> On 04/30/2013 08:39 PM, rohan.henry at cwjamaica.com wrote:
>>> 
>>>> I want to integrate Radiator into my NavisRadius production platform. How can I configure Radiator to use NavisRadius USS? Thanks.
>>> 
>>> NavisRadius seems to be a RADIUS server, so I'd think you could use
>>> <AuthBy RADIUS> to send requests to NavisRadius. Radiator would be a
>>> client for NavisRadius.
>>> 
>>> Or if you need to accept RADIUS requests from NavisRadius, you would
>>> configure NavisRadius as client, <Client ip.of.navis.radius>, in
>>> Radiator configuration file.
>>> 
>>> Unfortunately I am not familiar with NavisRadius, so I can not say
>>> exactly what is needed. The both cases above assume that Radiator and
>>> NavisRadius communicate with each other with normal RADIUS proxying.
>>> 
>>> Thanks,
>>> Heikki
>>> 
>>> -- 
>>> Heikki Vatiainen <hvn 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.
>>> _______________________________________________
>>> radiator mailing list
>>> radiator at open.com.au
>>> http://www.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 etc. 
>> Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc.
>> 
> 
> Rohan
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.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 etc. 
Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc.