geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1930) Make security realm types into GBeans so they can be added in new/updated configurations
Date Tue, 02 Jan 2007 21:49:27 GMT


Aaron Mulder commented on GERONIMO-1930:

Right now you can't add new login module types to the console dynamically.  We have to manually
configure each type of login module that a user should be able to select/configure in the
security realm screen in the console.

It would be better if there was a GBean that represented a login module type, like we now
have for database drivers, etc.  That way, if someone develops a new login module, they can
distribute it in a plugin that includes one of the GBeans described here, and then anyone
who installs that can use the console to create/configure login modules of that type for their
security realms.

So the GBean should have properties like the friendly name of this type of login module, the
implementation class name, a list of possible configuration properties (with type, description,
and required flag for each), and so on.  Then the console can build a list of login modules
dynamically and build the screens for whatever the user selects (though perhaps still supporting
an override flag, e.g. the current DB module uses a special screen rather than dynamically
building one).

Then we'd change the console to include GBeans of this type for the standard login module
types (DB, LDAP, properties file, etc.).

> Make security realm types into GBeans so they can be added in new/updated configurations
> ----------------------------------------------------------------------------------------
>                 Key: GERONIMO-1930
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: console, security
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>             Fix For: 1.x

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message