Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Date: Wed, 02 May 2007 14:21:37 -0400
From: Fred Dushin <fred@dushin.net>
Subject: Re: HTTP (Proxy) Authorization Policy
In-reply-to: <4638A863.7020502@iona.com>
To: cxf-dev@incubator.apache.org
Message-id: <A42CD309-3A8D-4661-944A-F8C8BD0FAE25@dushin.net>
MIME-version: 1.0 (Apple Message framework v752.3)
Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-transfer-encoding: 7bit
References: <463755BA.6060701@iona.com> <4638A863.7020502@iona.com>

Sounds like a flesh-and-blood bug to me, so I'd file it.

On May 2, 2007, at 11:04 AM, Polar Humenn wrote:

> Does anybody mind if I file a JIRA on this issue?
> -Polar
>
> Polar Humenn wrote:
>> Greetings,
>>
>> Currently the HTTP Authorization Policy is set on the Bus,  
>> Endpoint, Message etc. maps by keying it on its class.
>>
>> The problem is that the AuthorizationPolicy class is used for both  
>> the user authorization and proxy authorization.  Therefore the  
>> "proxy" authorization policy can't be set by this method.
>>
>> This could easily be fixed by creating a trivial extension
>>
>> public class ProxyAuthorizationPolicy extends AuthorizationPolicy {}
>>
>> There may be a little work to make spring config work, i.e.  
>> setProxyAuthorization(), but not much.
>>
>> What are people's thoughts?
>>
>> Cheers,
>> -Polar
>
>