[
https://issues.apache.org/jira/browse/GERONIMO-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713868#action_12713868
]
David Jencks commented on GERONIMO-4505:
----------------------------------------
This ought to be a little easier now after GERONIMO-4553 if you make the new
security realm non-global. Then you can use an artifact-alias to your plugin
to replace it.
I think the PropertiesLoginModuleManager is still an infuriating problem.
We definitely need some good instructions no matter how hard it is to do.
> console-tomcat references directly to properties-login
> ------------------------------------------------------
>
> Key: GERONIMO-4505
> URL: https://issues.apache.org/jira/browse/GERONIMO-4505
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.1.3
> Environment: Ubuntu Linux 8.04 (kernel 2.6.24-22-generic)
> Sun JDK 1.6.0-11
> Reporter: Uwe Plonus
>
> It's nearly impossible to replace the server-security-config with an own as
> long as the console is deployed.
> The console has a module {{base-portlets.war}} which references to the
> {{LoginModule}} {{propterties-login}} which must be available during start up
> else the server start up will be terminated with an error that the named
> reference is missing. Also this module expects a
> {{PropertiesLoginModuleManager}} as LoginManager.
> At least the start up of the server should not fail if the {{LoginModule}}
> {{properties-login}} does not exist.
> To work around this issue I had to include a GBean with the name
> {{properties-login}} in my security config. Then I can replace the default
> login module complete.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
