(RADIATOR) Interoperation with both GRIC and iPass

[Hugh Irvine]

Hello Igor -

There are two scenarios to look at here - the first is inbound 
authentication requests from your users who are travelling and using 
GRIC and IPASS services. This is simply a matter of configuring the 
appropriate Client clauses in your Radiator configuration file to deal 
with the incoming requests.

The second scenario is slightly more difficult - travelling users who 
are using your infrastructure to dial up and you need to forward the 
athentication requests to either GRIC or IPASS depending on which 
service they want to use. This is usually done by having those users 
employ prefixes in the usernames indicating which they want to use.

Something like this:

	IPASS\username at some.realm

or

	GRIC\username at some.realm

You should check with both GRIC and IPASS to see what they suggest (and 
already use).

regards

Hugh


On Sunday, Aug 17, 2003, at 20:04 Australia/Melbourne, Igor Briski 
wrote:

>
> Has anyone solved a situation where both iPass and GRIC roaming users 
> are
> authenticating on the same radiator server?
>
> How do I distinguish GRIC and iPass users from each other, how do I 
> tell
> which user to authenticate with GRIC and which with iPass?
>
> Both systems have the same format username at realm, so obviously I need 
> some
> other attribute to know which user is an iPass user and which user is 
> a GRIC
> user.
> -- 
> Igor Briski -- igor.briski at iskon.hr
>
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
>
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.