You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/08/26 20:34:26 UTC
[jira] Created: (GERONIMO-925) separate security gbeans into a separate plan
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
[jira] Closed: (GERONIMO-925) separate security gbeans into a separate plan
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-925?page=all ]
David Jencks closed GERONIMO-925:
---------------------------------
Resolution: Fixed
done, rev 278940
> 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
> Assignee: 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