(RADIATOR) Validation of multiple MSISDNs against one user na me

[Cockerell Martin (UK)]

Hi Ingvar,

Thanks for the suggestion to use LDAP - I'll look into that further.
Unfortunately I think that I will still need to use username/password
validation as well as I only require this capability for a subset of the
users accessing our environment through a single access point; currently I
segregate the various groups of users into domains and only apply this
processing to one domain.

Regards,
Martin

-----Original Message-----
From: Ingvar Berg (LI/EAB) [mailto:ingvar.berg at ericsson.com] 
Sent: 14 July 2004 07:53
To: 'Cockerell Martin (UK)'; 'radiator at open.com.au'
Subject: RE: (RADIATOR) Validation of multiple MSISDNs against one user name

Hi Martin,

If you use an LDAP directory, you can have multiple instances of the MSISDN
attribute for each user. Index it for exact match (and probably uniqueness),
then you can get all the user details (like IP address) you need by
searching for the MSISDN in the request. And as the MSISDN _is_ the user
identification, you can forego the uid/pw stuff alltogether.
You don't need to do any special hooks, just specify in the Authby LDAP2
that MSISDN is the authenticator:
  SearchFilter (mobile=%{Calling-Station-Id})
and skip the username and password parameters.

/Ingvar

>  -----Original Message-----
> From: 	owner-radiator at open.com.au 
> [mailto:owner-radiator at open.com.au]  On Behalf Of Cockerell 
> Martin (UK)
> Sent:	den 13 juli 2004 18:39
> To:	'radiator at open.com.au'
> Subject:	(RADIATOR) Validation of multiple MSISDNs 
> against one user name
> 
> I have been experimenting with using Radiator to assign a 
> fixed IP address to an incoming connection based on MSISDN; 
> however, at present I seem to need a full entry in the users 
> file for each MSISDN (either a separate username with 
> Calling-Station-Id added as an extra check parameter or 
> substituting Calling-Station-Id for username as shown in the 
> MSISDN.hook goodies file).
> 
> Ideally what I would like to do is have a single 
> username/password combination for a group of users, with the 
> allocated IP address being determined by the individual 
> MSISDN - this is to allow me to support several large groups 
> of users where the main requirement is to validate an 
> individual MSISDN and assign the same IP address every time.
> 
> I am hoping to pass maintenance of the MSISDN/IP address list 
> to someone less technical than my support team.  I'm 
> beginning to think that the most reliable way of handling 
> this is with a simple SQL table (with some form of web 
> front-end) that Radiator uses to look-up the IP address.  Can 
> anyone think of a better way?
> 
> Regards,
> Martin Cockerell
> 
> ADE Trials and Architecture Manager
> O2 Limited
 



-----------------------------------------------------------------------

========================================================
This electronic message contains information from the mmO2 plc Group 
which may be privileged or confidential. The information is intended to
be for the use of the individual(s) or entity named above. If you are not
the intended recipient be aware that any disclosure, copying
distribution or use of the contents of this information is prohibited. If you
have received this electronic message in error, please notify us
by telephone or email (to the numbers or address above) immediately.
========================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20040714/4470e028/attachment.html>