Hi Felipe,
OAuth is about 2 things: delegated authorization through a redirect-
based flow
and securing HTTP messages. The part that's been hosted in Jersey
relates
to the securing of HTTP messages (i.e. signing -on the client side- and
verifying -on the server side- digital signatures as specified in
OAuth).
Note that the digital signature mechanism discussed here (OAuth) is
*not*
the same you'll find in Glassfish Enterprise since the latter provides
*XML* digital signature. In fact, most security mechanisms in Glassfish
relates to WS-Security which is quite another "beast" since it focuses
on SOAP-level messaging as opposed to HTTP-level concerns addressed
in OAuth. I wouldn't say one is better than the other, they just
address 2 different messaging approaches.
As for sample, code, I'll let Paul (Bryan) respond but if you check the
Javadoc of the OAuth source code we've checked in under Jersey's tree
you'll see explanations including examples of usage.
Hope This Helps,
Hubert
On Jun 3, 2009, at 3:44 PM, Felipe Gaúcho wrote:
> I am attending a nice presentation with the creator of OAuth, and he
> quoted some code using Jersey annotations, etc...
>
> questions: is it better than use the Glassfish security mechanisms ?
>
> and other: do you have a sample code ?
>
> --
> Looking for a client application for this service:
> http://fgaucho.dyndns.org:8080/footprint-service/wadl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
--
Hubert A. Le Van Gong
Identity Architect
Sun microsystems, Inc.
17 Rue Duprey
Grenoble, 38000
France
--------------------------------------------------
email: hubert.levangong_at_sun.COM
tel:+33 4 7663 0935
blog: http://blog.levangong.com/
N 45 12.011'
W 005 44.217'