[reSIProcate] DUM Auth

[Scott Godin]

Yes - or you could implement onReadyToSend for the various usages.

 

From: Roee Vulkan [mailto:vulkanr at gmail.com] 
Sent: Tuesday, January 09, 2007 12:24 PM
To: Scott Godin; resiprocate-devel at list.resiprocate.org
Subject: Re: [reSIProcate] DUM Auth

 

 

Just a thought - will I be able to do it by assigning an output message
decorator that will simply add the relevant header?

 

	----- Original Message ----- 

	From: Scott Godin <mailto:slgodin at icescape.com>  

	To: Roee Vulkan <mailto:vulkanr at gmail.com>  ;
resiprocate-devel at list.resiprocate.org 

	Sent: Tuesday, January 09, 2007 6:10 PM

	Subject: RE: [reSIProcate] DUM Auth

	 

	Transactions should only go through the authorization process if
they are the first client transaction of a dialogset.  All requests
within the same dialogset should contain the proxy auth header from the
first challenge.    There is currently no way to get dum to include the
auth headers on all new client requests.

	 

	From: resiprocate-devel-bounces at list.resiprocate.org
[mailto:resiprocate-devel-bounces at list.resiprocate.org] On Behalf Of
Roee Vulkan
	Sent: Tuesday, January 09, 2007 10:15 AM
	To: resiprocate-devel at list.resiprocate.org
	Subject: [reSIProcate] DUM Auth

	 

	 

	Hello.

	 

	After successfuly being authenticated with the proxy, Is there a
way to make DUM use the same "Proxy-Authorization" string on subsequent
calls?

	 

	Currently every transaction is going through the whole
authentication process.

	 

	Thanks.

	-Roee.

	 

	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070109/51133685/attachment.htm>