Hello Heikki,
> Date: Wed, 24 Aug 2011 11:12:16 +0300
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: [RADIATOR] EAP-SIM Authentication
>
> Hmm, what does the User-Name attribute look like. Isn't IMSI part of the
> username part?
Below is a snippet from the first Access-Request:
User-Name = "3d860eab069282e65" EAP-Message =
<2><0><0>9<1>[email protected]
The username contains the TMSI. In which RADIUS attribute I can exactly find
the IMSI?
> If not, you could take a look at the goodies/ examples in the SIM pack.
> The example configurations show there's AuthorisedHook which might be
> useful:
>
> # AuthorisedHook is called when the SIM request is completely
> # authorised, and before the Access-Accept is returned.
>
> One of the parameters is a pointer to EAP context Radiator keeps and the
> IMSI should be available from the context information.
Are you saying that I only have to uncomment the below line from the
configuration?
AuthorisedHook sub {print "here in AuthorisedHook @_\n";}
Moving forward on the EAP-SIM authentication, if I am going to try
authenticating via the API of the MAP gateway, I should only be using the
"AuthBy EXTERNAL" and execute a script whenever there is an Access-Request and
I don't need the configurations of the "AuthBy SIMOPERATOR" anymore, right?
Please advice. Thank you once again. _______________________________________________
radiator mailing list
[email protected]
http://www.open.com.au/mailman/listinfo/radiator
