geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Closed: (GERONIMO-639) GenericSecurityRealm doesn't express its gbean dependencies
Date Fri, 29 Apr 2005 21:31:57 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-639?page=all ]
     
David Jencks closed GERONIMO-639:
---------------------------------

     Resolution: Fixed
    Fix Version: 1.0-M4

fixed in geronimo rev 165344 and in openejb using the "lots of little linked gbeans" solution.

> GenericSecurityRealm doesn't express its gbean dependencies
> -----------------------------------------------------------
>
>          Key: GERONIMO-639
>          URL: http://issues.apache.org/jira/browse/GERONIMO-639
>      Project: Geronimo
>         Type: Bug
>   Components: security
>     Versions: 1.0-M3
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.0-M4

>
> A GenericSecurityRealm depends on a bunch of LoginModuleGBeans to express the login modules
that must be logged into to log into the realm.  Currently these are listed by gbean name
+ other info in a properties file format.  This does nothing to assure that the login modules
are in fact started before the GSR is started, although the LMs are used in the GSR constructor.
> Sometimes the GSR will start, but the same configuration sometimes will not start due
to system variations in gbean start order.
> One solution is to make a LoginModule holder gbean that forms a linked list of gbeans,
similar to the JettyFilterMapping.  This can be implemented easily with no core changes, but
it results in a profusion of gbeans that do almost nothing.
> Another possible solution is to introduce a core gbean feature that lets you have something
like an ordered list of explicit references, all of which must be started for the gbean to
start.  This would be of more general use but would require some thought to figure out the
best functionality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message