On 25/04/07, Zoran Avtarovski <[EMAIL PROTECTED]> wrote:
For what it's worth we use a combination of both JAAS and a custom
AuthInterceptor.
JAAS handles authentication and the AuthInterceptor manages authorisation.
This leverages off the strength of JAAS and has the flexibility required for
our
For what it's worth we use a combination of both JAAS and a custom
AuthInterceptor.
JAAS handles authentication and the AuthInterceptor manages authorisation.
This leverages off the strength of JAAS and has the flexibility required for
our needs.
A couple of sources of useful information are:
1.
On 4/24/07 8:49 AM, "Shahak Nagiel" <[EMAIL PROTECTED]> wrote:
> Others can chime in as well, but from my experience in the past,
> container-managed authentication is a little too rigid and doesn't offer
> anywhere near the flexibility of a custom-brewed authentication/authorization
> scheme. Th
Others can chime in as well, but from my experience in the past,
container-managed authentication is a little too rigid and doesn't offer
anywhere near the flexibility of a custom-brewed authentication/authorization
scheme. That's not to say a "custom" scheme need be entirely proprietary; we
j
4 matches
Mail list logo