Keycloak integration

Le 23/12/2014 10:24, Juraci Paixão Kröhling a écrit :
> Not really, but the username/password can be checked automatically,
> similar to what the adapter itself does. So, we could leave this
> specific endpoint unprotected, and then manually do a "basic" auth on
> another special endpoint, just to check if the user has the permission
> to do what he's trying to do. I'll try to think about other solution for
> it though.

Is "web-resource-collection"'s "url-pattern" mechanism powerful enough 
to express that `/tenants/{tenantId}/*` should be protected, but 
`/tenants/{tenantId}/influx/series` should not? Note that `{tenantId}` 
here is the JAX-RS notation for a path parameter.

What do you mean by "manually do a basic auth"?