Fair question. Let's consider client side first. For authentication,
JAAS provides a pluggable way of collecting the credentials from the
user. However with OAuth 2.0, we don't want the client app to collect
the credentials...we want the client app to redirect the resource
owner to an authorization server to authenticate and grant access to
the client app. I don't think this type of authorization on the
client side lines up with JAAS.
On the server side, I think there is more opportunity for integration,
ideally with the annotations that are already available. Another
challenge though is that OAuth brings another party to the
transaction. Rather than just AuthN/AuthZ of the client by the
resource, we also have to AuthZ the resource owner who is using the
client. Specifically, we need to authorize that the resource owner
has access to the resource AND that the client has been granted access
to the resource on behalf of the resource owner.
I don't want to reinvent the wheel if it's already there...I'll give
JAAS another look and see if any other folks are having better luck
with using it with OAuth 2.0.
-Casey
On Fri, Dec 12, 2014 at 2:45 PM, Markus KARG <markus_at_headcrashing.eu> wrote:
> Casey,
>
> I am not a security guy at all, so please don't mind if the question is dumb, but doesn't JAAS already define interfaces for authentication providers? If so, we could use those instead of reinventing the wheel.
>
> Regards
> -Markus
>
> -----Original Message-----
> From: Casey Lee [mailto:cplee_at_nektos.com]
> Sent: Freitag, 12. Dezember 2014 17:53
> To: jsr370-experts_at_jax-rs-spec.java.net
> Subject: JAX-RS Security
>
> I have some opinions on opportunities for adding security to JAX-RS.
> First, on the client side I'd love to see a method added to Invocation.builder to add an implementation of a new interface named AuthorizationProvider. This would allow implementations of AuthorizationProvider to be created for specific types of authz...like OAuth2AuthorizationProvider or BasicAuthorizationProvider. These providers would be responsible for applying necessary Authorization header (or query params?) to the invocation. What are the thoughts on adding some standard providers to the API? OAuth 2.0 for example is something that has become ubiquitous, but has a steep learning curve for developers to use properly.
>
> On the server side aren't the JSR-250 security annotations supported by JAX-RS? Or is that only implemented by some specific vendors?
> Seems that those solve course grained security (by role). We have chosen to leverage those annotations and treat OAuth 2.0 scopes as roles. Would it make sense to have a more OAuth 2.0 specific solution (@ScopesAllowed)?
>
> -Casey
>