Hi Paul,
This OAuth support should be really interesting!
Create a branch in the "branches" area.
The best location for the OAuth stuff would be in the contribs area.
If you anticipate this is going to contain multiple projects as you
indicate then i recommend that the "oauth" in contribs be a parent
module, for example:
jersey/contribs/jersey-oauth
client
digsig
Please include unit tests.
As soon as you consider things to be stable we can merge the branch to
the trunk, then it will be continuously tested by Hudson, and we can
align with a stable release.
If you want the branch to be continuously built and tested we can also
arrange for that.
Paul.
On Apr 27, 2009, at 11:21 PM, Paul C. Bryan wrote:
> Hi Devs:
>
> Hubert Le Van Gong and I are working on an implementation of an OAuth
> policy enforcement point and token services, as extensions to the
> OpenSSO project.
>
> During the course of our development, it became apparent that we will
> need client-side support for OAuth, to allow client-side OAuth digital
> signatures to be created for outgoing JAX-RS requests.
>
> I'd like to propose I create a branch of Jersey project to implement
> two
> extensions:
>
> 1. A Jersey client filter that implements the OAuth authentication in
> the HTTP Authorization header, basically following the functionality
> of
> HTTPBasicAuthFilter.
>
> 2. The OAuth digital signature library, which can generate a JAR file
> that will be used by the OAuth authentication filter, as well as the
> OpenSSO policy enforcement points and/or token services.
>
> Please let me know if this can go forward, and if so, how you'd prefer
> me to branch to accommodate these.
>
> Thanks,
>
> Paul
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: dev-help_at_jersey.dev.java.net
>