[ http://issues.apache.org/jira/browse/JS2-300?page=all ]
Michael Lipp updated JS2-300:
-----------------------------
Attachment: JBossLoginModule.patch
> Request to make login modules more flexible
> -------------------------------------------
>
> Key: JS2-300
> URL: http://issues.apache.org/jira/browse/JS2-300
> Project: Jetspeed 2
> Type: Improvement
> Environment: JBoss/HSQLDB
> Reporter: Michael Lipp
> Attachments: DefaultLoginModule.patch, JBossLoginModule.patch
>
> In order to proceed with JS2-297, I'd like to see the attached patch (against
> M3) applied. It allows a UserManager to be passed to DefaultLoginModule and
> JBossLoginModule.
> As described in JS2-297, my goal is to make the user/group/role components of
> Jetspeed available as a JetspeedSecurityService MBean (i.e. as "application
> server extensions"). This MBean can then provide a UserManager. A login
> module based on this service would obtain the MBean, get the UserManager and
> use it in its login module (quite straight-forward). The current
> implementation of DefaultLoginModule "insists" on obtaining the UserManager
> via a LoginModuleProxy that is instantiated for the single purpose of holding
> a static reference to the UserManager (this is marked as a hack in the
> comment, and rightly so). While I can, of course, keep instantiating a
> LoginProxy, there is really no reason for doing this. And of course, I'd like
> to avoid duplicating DefaultLoginModule and JBossLoginModule.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
