dev@jersey.java.net

Re: [Jersey] Jersey-OAuth implementation

From: Paul C. Bryan <pbryan_at_sun.com>
Date: Mon, 04 May 2009 16:57:08 -0700

Hi Devs:

I've created a new branch:

  https://jersey.dev.java.net/svn/jersey/branches/oauth-extensions/

In this branch, I've checked-in the initial code dump for the OAuth
digital signature library, including an initial unit test:

  jersey/contribs/jersey-oauth/oauth-sig/

As I'm relatively new to Jersey and Maven, I would appreciate some
feedback on whether I got this right, or if the work is in need of
revision.

Thanks,

Paul

On Mon, 2009-05-04 at 18:24 +0200, Paul Sandoz wrote:
> On May 4, 2009, at 6:16 PM, Paul C. Bryan wrote:
>
> > We're getting close to the point where it will make sense to check
> > some
> > code in. I'm currently thinking of the following project structure.
> >
> > /jersey/contribs/jersey-oauth
> > oauth-sig (OAuth signature library)
> > oauth-client (Jersey client filter)
> > oauth-server (Jersey server request wrapper)
> >
> > Will this work?
> >
>
> Looks good to me.
>
> Paul.
>
> > Paul
> >
> > On Tue, 2009-04-28 at 10:41 +0200, Paul Sandoz wrote:
> >> 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
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe_at_jersey.dev.java.net
> >> For additional commands, e-mail: dev-help_at_jersey.dev.java.net
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe_at_jersey.dev.java.net
> > For additional commands, e-mail: dev-help_at_jersey.dev.java.net
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: dev-help_at_jersey.dev.java.net
>