For the following steps we assume that the openCRX administrator has configured the users admin-Root, admin-Standard and guest with the appropriate roles on the application server. In the case of JBoss he would have edited the files openCRX.users.properties and openCRX.roles.properties in directory ./jboss-4.0.1/server/default/conf as follows and then restarted the application server:
Example 3-1. openCRX.users.properties with user=password syntax.
admin-Root=rootSecret admin-Standard=adminSecret guest=guest
Example 3-2. openCRX.roles.properties with user.Roles=role1,role2 syntax.
admin-Root.Roles=OpenCrxRoot admin-Standard.Roles=OpenCrxAdministrator guest.Roles=OpenCrxUser
Before a user can login to openCRX you must first create a new login at the application server level. Of course you can automate this process. E.g. on JBoss you can replace the file-based org.jboss.security.auth.spi.UsersRolesLoginModule login module with the database login module org.jboss.security.auth.spi.DatabaseServerLoginModule and configure it to access the openCRX security tables security_Principal and security_Credential. Please refer to the JBoss installation guide if you want to make use of the database login module.
Before we get started with setting up openCRX it is helpful if you know that - by default - there are three types of users playing quite different roles in the context of openCRX:
Figure 3-1. Data in the openCRX database can be partitioned into data segments.
All users who access openCRX by the same web application (e.g. opencrx-core-CRX) also share the same customization files (user interface, code tables, basic data). The openCRX/Core README explains how to setup multiple customized web applications..
The following sections explain: