geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Created: (GERONIMO-497) Improve DeploymentSupport setting on a realm
Date Tue, 23 Nov 2004 02:32:18 GMT
Improve DeploymentSupport setting on a realm
--------------------------------------------

         Key: GERONIMO-497
         URL: http://nagoya.apache.org/jira/browse/GERONIMO-497
     Project: Apache Geronimo
        Type: Bug
  Components: security  
    Versions: 1.0-M4    
    Reporter: Aaron Mulder


The GenericSecurityRealm currently provides DeploymentSupport features if the login modules
implement DeploymentSupport.  It would be nice to support an external DeploymentSupport, set
as a property on the GenericSecurityRealm.  Currently that ability is there (on DS per login
domain for the realm), but it just expects to get a class name, and this doesn't really work
as the DeploymentSupport instance has no way of being configured (e.g. to point to a specific
DB, LDAP server, etc.).  Probably, a DeploymentSupport defined separately from the realm should
be instantiated and configured as a GBean, and the realm given the ObjectName instead of the
class name.  However, I'm not 100% convinced that "GBean creep" is the way to go here.  We
could also add the same initialize method declared in LoginModule to DeploymentSupport, and
then provide a way to send Options to the DeploymentSupport on the realm, but that seems pretty
complex too.

-- 
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


Mime
View raw message