This article is about how to replace default .properties realm
geronimo-admin with SQL or LDAP realms.
By default, Geronimo is using a .properties file realm for authentication named
geronimo-admin, which is used by JMX server, Administration Console, Online-deploy and MEJB applications. However, you may not want to use it for production use. Alternatively, you can use database or LDAP realms in a production environment. To demonstrate how to replace the default realm, we will use two samples as followed:
With a database-based realm
In this example, we will use an embedded Derby database as the security provider.
- Create a database named
SecurityDatabaseusing DB manager in the administration console.
- Create two tables
Groupsto store user credential and group information. In the DB manager portlet copy and paste the above SQL into SQL Commands box and select the
SecurityDatabasedatabase and press Run SQL button to create the tables.
- Create an Derby embedded XA database pool named
SecurityDatabasePoolusing Database Pools portlet under Datasources in the console. Make sure to specify the Database Name as
- Stop the server and update module
$GERONIMO_HOME/var/config/config.xmlfile to enable the SQL realm. Make sure to substitute
VERSIONstring with the appropriate Geronimo version. Where
- geronimo_admin is the same realm name as the original one. You might use another name instead, by doing so, you have to replace the security realm name in all other applications that were using the same security constraint as console.
- Restart the server and try to login with user name userone and password p1. You will see the newly created SQL realm working.
With a LDAP-based realm
To replace the default .properties file realm using a LDAP realm, the configuration is nearly identical to the sample above. The only difference is to use
LoginModuleClass. Here is the code snippet you can use in
config.xml. Make sure to substitute
VERSION string with the appropriate Geronimo version.