Re: [jboss-as7-dev] Security Domain Config: JASPI vs Classic?
Right now I'm preserving the existing layout of two separate sections, I
was just wondering if there was any benefit I was missing. For example,
is the authorization -> authentication reference a problem for classic auth?
On 10/3/11 8:43 AM, Marcus Moyses wrote:
Do you plan to make those attributes optional or mandatory? I guess
if
they were optional there would be no problem to merge the
configurations. Making them required would add some confusion to
customers I guess.
Anyway, Stefan implemented the JASPI integration last week and was about
to send a pull request so you might want to check with him so your
commits don't conflict.
On 10/03/2011 02:28 AM, Jason T. Greene wrote:
> Right now the security domain configuration has separate sections for
> JASPI and Classic/Basic authentication. The only difference seems to
> be that JASPI authentication requires an additional name field per
> module, and JASPI authorization requires an additional login-module
> reference. So essentially its a superset.
>
> Is there a reason we would not want to just switch to the JASPI style
> of specification, and eliminate the classic style. A name per login
> module seems useful anyway.
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat