On 3/20/07, Pekka Pessi <[EMAIL PROTECTED]> wrote:
> Hi Jan,
>
> 2007/3/19, Jan Van den bosch <[EMAIL PROTECTED]>:
> > So far, I've tried this:
> >
> > nua_set_params(nua, SIPTAG_AUTHORIZATION(NULL), TAG_END());
> > nua_set_hparams(nh, SIPTAG_AUTHORIZATION(NULL), TAG_END());
> >
> > both in my nua_r_register() callback, and this:
> >
> > nua_unregister(op->op_handle, SIPTAG_AUTHORIZATION(NULL), TAG_NULL());
> >
> > in my unregister method. Still no luck, I'm afraid. :( Can someone help me
> > out here? It's driving me mad.
>
> I'm afraid the current nua code does not allow one to remove the
> authorization headers from the request. The SIPTAG_AUTHORIZATION(NULL)
> trick you tried could be a nice API for indicating the stack that it
> should not add the authorization header on its own, however, I think
> you expect stack to add one later when it gets the challenge from the
> server?
Yeah, I figured it would work in the same way as in this example:
nua_set_params(nua,
SIPTAG_USER_AGENT_STR("tester/1.0"),
SIPTAG_ALLOW_STR("INVITE,CANCEL,BYE,ACK"),
SIPTAG_ORGANIZATION(NULL),
SIPTAG_USER_AGENT(NULL),
SIPTAG_ALLOW(SIP_NONE),
TAG_END());
What if I take care of the Digest response myself and add the
Authorization header through a SIPTAG_UNKNOWN tag? Can I strip the
(unknown) Authorization header off when I get a 200/OK response? How
do I do that, exactly?
> An extra tag to nua_authenticate() is probably needed.
>
> By the way, do you get an Authentication-Info header in the 200 OK
> response to the initial INVITE?
In the 200/OK response to the initial REGISTER, you mean? No, it
doesn't contain an Authentication-Info header.
Thanks,
Jan
>
> --Pekka
>
>
> >
> > Thanks,
> > Jan
> >
> >
> > On 3/16/07, Jan Van den bosch <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > Apparently, nua_authenticate attaches credentials to an operation so they
> > can be re-used in the future. However, my application requires that
> > re-REGISTERs/un-REGISTERs start from a clean REGISTER message (without a
> > WWWAuthentication header). Is there a way to keep a re-REGISTER from sending
> > an Authorization header with it and make it repeat the HTTP Digest sequence?
> > >
> > > Thanks,
> > > Jan
> >
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Sofia-sip-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
> >
> >
>
>
> --
> Pekka.Pessi mail at nokia.com
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
