You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2004/11/20 08:50:26 UTC

[jira] Resolved: (GERONIMO-422) SimpleSecurityRealm.options and ConfigurationEntryRealmLocal.options seem redundant

     [ http://nagoya.apache.org/jira/browse/GERONIMO-422?page=history ]
     
Aaron Mulder resolved GERONIMO-422:
-----------------------------------

     Resolution: Fixed
    Fix Version: 1.0-M4

Now the options live solely in the LoginModuleGBean configuration, and the flag lives solely in the GenericSecurityRealm configuration.

> SimpleSecurityRealm.options and ConfigurationEntryRealmLocal.options seem redundant
> -----------------------------------------------------------------------------------
>
>          Key: GERONIMO-422
>          URL: http://nagoya.apache.org/jira/browse/GERONIMO-422
>      Project: Apache Geronimo
>         Type: Bug
>   Components: security
>     Versions: 1.0-M2
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>      Fix For: 1.0-M4

>
> If you use a custom LoginModule with a SimpleSecurityRealm, there are two ways to provide options to the LoginModule.  One is to set the options property on SimpleSecurityRealm.  The other is to set the options property on the ConfiguraitonEntryRealmLocal when you deploy a JAAS configuration for the realm.
> It doesn't seem like we need both ways to specify options to the login module.  I think we could remove the options property from SimpleSecurityRealm, and just use the options on the ConfigurationEntryRealmLocal.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira