Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Message-ID: <106138388.1119496810645.JavaMail.jira@ajax.apache.org>
Date: Thu, 23 Jun 2005 05:20:10 +0200 (CEST)
From: "David Sean Taylor (JIRA)" <jetspeed-dev@portals.apache.org>
To: jetspeed-dev@jakarta.apache.org
Subject: [jira] Resolved: (JS2-300) Request to make login modules more
 flexible
In-Reply-To: <1625953487.1119444557435.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JS2-300?page=all ]
     
David Sean Taylor resolved JS2-300:
-----------------------------------

    Fix Version: 2.0-M4
     Resolution: Fixed

patch applied

> 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
>     Assignee: David Sean Taylor
>      Fix For: 2.0-M4
>  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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org