cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schneider <>
Subject Re: Request for feedback: Refactoring of HTTP client authentication
Date Thu, 23 Dec 2010 22:49:36 GMT
Ok .. I guess it is better to not mess with this feature. I will shortly 
prepare another patch to
remove the dependency to HttpConduit from the HttpAuthSupplier. Instead 
I will add AuthorizationPolicy.
So the interface is also usable for the proxy auth. It already seems to 
work quite well for me.
I will post some more details in a separate thread.


Am 23.12.2010 04:41, schrieb Daniel Kulp:
> I like it.  Looks fine by me.    The only "concern" I have is with:
>> Additionally I would like to remove the feature of setting an
>> AuthorizationPolicy on the message. This would allow us to make the
>> authsuppliers independent of conduit and message in the future.
> as that would likely break a bunch of things.    For one, how do you plan on
> having the JAX-WS username/password properties?   Currently, we map those
> directly onto and AuthorizationPolicy object on the message.  Thus, that
> interaction would need to change as well.
> Dan


View raw message