Re: [reSIProcate] Authentication challenge issue

["Niraj Roy" <nroy@xxxxxxxxxx>]

Hi,
        That will be fine I can do that.
        But this implementation leads us to think that inter domain call
keeping authentication on will not be possible for any user.
        Because in general it will never happen that Request Uri will
contain anything from 'From' header specially domain.

Niraj
-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Daniel
Pocock
Sent: Thursday, February 15, 2007 6:04 PM
To: 'resiprocate-devel'
Subject: Re: [reSIProcate] Authentication challenge issue



Niraj Roy wrote:
> Hi,
>       One issue with Authentication.
>       I have created a profile for user Bob with the domain name
> 'biloxy.com'.
>       Bob is trying to place a call to hirel@xxxxxxxxxx
>       Hence 'Request Uri' and 'To' header will contain 'hirel@xxxxxxxxx'
>       And From header will contain 'Bob@xxxxxxxxxx'.
>       In the current implementation while challenging ServerAuthManager
> use Request Line for supplying realm. Hence 407 Challenge responses
contain
> 'cisco.com' in the required realm.
>       Bob resends INVITE request 'cisco.com' in it's realm.
>       But his profile domain is set to 'biloxy.com' hence
> ServerAuthManager sends 404 Error response.
>       
>       I think ServerAuthManager should take realm from the 'From' header
> instead of Request Line..
>       
>       Any guess...?
>   

You can write your own sub-class of ServerAuthManager, call it 
MyServerAuthManager for instance.

These virtual methods need to be implemented with your own logic:

      virtual bool authorizedForThisIdentity(const resip::Data &user,
                                             const resip::Data &realm,
                                             resip::Uri &fromUri);

      virtual const Data& getChallengeRealm(const SipMessage& msg);

      virtual bool isMyRealm(const Data& realm);


>       
>       Niraj
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>   
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

__________ NOD32 2062 (20070215) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com