Page History

Where is the security configuration?

In a normal geronimo Geronimo server, the basic security configuration is divided into two plugins, j2ee-security and server-security-config. The stuff parts you are not too likely to want to change, such as the jacc provider and the keystore manager, are in j2ee-security. The stuff parts that you are almost certain to want to change is in server-security config. For instance, the toy properties file security realm for the admin console is in server-security-config.

...

You want to replace server-security-config with your own geronimo Geronimo plugin (see Plugin infrastructure) that contains a security realm customized for your security setup (e.g. ldap) , and includes whatever keystores you need. To make your plugin replace all uses of server-security-config with your plugin, you need to include an artifact-alias element in your geronimo-plugin.xml file.

<artifact-alias key="org.apache.geronimo.framework/server-security-config/2.2-SNAPSHOT/car">com.myco/myco-security-config/1.0/car</artifact-alias>
<artifact-alias key="org.apache.geronimo.framework/server-security-config//car">com.myco/myco-security-config/1.0/car</artifact-alias>

or if you save time and effort and Another option is to use maven with the car-maven-plugin you'd include this in your . The above code would need to be included in the car-maven-plugin configuration in your pom.xml.

Note that if you want the admin console and MEJB to continue working without redeployment, you have to include a security realm named geronimo-admin that supplies . geronimo-admin should supply supply appropriate users with principals of class org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal and names of (as appropriate) admin (for console and MEJB read access) and mejbadmin (for MEJB write access).

...