Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <608732795.1125081266131.JavaMail.jira@ajax.apache.org>
Date: Fri, 26 Aug 2005 20:34:26 +0200 (CEST)
From: "David Jencks (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Created: (GERONIMO-925) separate security gbeans into a
 separate plan
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

separate security gbeans into a separate plan
---------------------------------------------

         Key: GERONIMO-925
         URL: http://issues.apache.org/jira/browse/GERONIMO-925
     Project: Geronimo
        Type: Bug
  Components: security  
    Versions: 1.0-M5    
 Reporter: David Jencks
 Assigned to: David Jencks 
     Fix For: 1.0-M5


If you need to use a nonstandard (non-geronimo) security policy implementation, currently you have to change the j2ee-server-plan to include the policy class or the SecurityService gbean will fail on startup.  You can work around this by including another SecurityService gbean in a plan that does include the policy class, but it seems a cleaner solution is to put the security gbeans in a separate plan that can be replaced when you need a different policy.  Since security will often need to be customized anyway, this should make it easier to see what you are likely to need to customize.

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