[
https://issues.apache.org/jira/browse/GERONIMO-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks reassigned GERONIMO-4603:
--------------------------------------
Assignee: (was: David Jencks)
I'm not going to have time to get this fixed for 2.2 but it is pretty easy and
would be great to get in.
> PropertiesLoginManager is hardwired to properties-login login module
> --------------------------------------------------------------------
>
> Key: GERONIMO-4603
> URL: https://issues.apache.org/jira/browse/GERONIMO-4603
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.1.4, 2.2
> Reporter: David Jencks
> Fix For: 2.1.5, 2.2
>
>
> In production you want to replace the toy properties login realm with
> something else such as an ldap realm. However the admin console has a
> hardwired dependency on the properties-login gbean.
> We should make the reference from PropertiesLoginManager multi-valued and
> scan through it for properties login modules so you can edit any such
> properties files.
> Workaround for replacing server-security-config with something with a real
> security realm is to include the properties login module as a dummy, not used
> in a security realm:
> <!-- bug workaround -->
> <gbean name="properties-login"
> class="org.apache.geronimo.security.jaas.LoginModuleGBean">
> <attribute
> name="loginModuleClass">org.apache.geronimo.security.realm.providers.PropertiesFileLoginModule</attribute>
> <attribute name="options">
> usersURI=var/security/users.properties
> groupsURI=var/security/groups.properties
> </attribute>
> <attribute name="loginDomainName">geronimo-admin</attribute>
> </gbean>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
