CSM Service & Admin UI Installation Guide

[ CSM: Administrators Guide | Developers Guide | Users Guide | caGrid: Documentation Guides ]

This guide provides step by step instructions for the installation of the Common Security Module (hereafter referred to as CSM) service and administrative interface. Source and binary distributions of the CSM service and admin interface software are availble on the Downloads page. Installation instructions for both distributions are included in this guide.

Prerequisites

In order to install and run the CSM Service and admin interface, the following prerequisite software must be installed:

Java 1.5+ JDK (download)
MySQL 5.0+ (download)

Note: If you choose to install MySQL on a Linux host, you should enable case insensitive table names to avoid query issues. Add the following to your my.cnf configuration file in the [mysqld] section:

lower_case_table_names=1

For more information on configuring MySQL to use case insensitive table names, refer to the Identifier Case Sensitivity section of the MySQL manual.

Step 1: Install caGrid 1.3

In this step you will download and install caGrid 1.3 using the caGrid Installer. If you already have caGrid 1.3 installed on your machine you may proceed to the next step. If you do not wish to use the installer, caGrid may also be installed manually. Note that if you have previously installed caGrid on your host and you would like to reinstall or upgrade to version 1.3, follow the re-installation preparation instructions. If you are installing caGrid on a host that is behind a firewall, it is possible to create an offline caGrid installer.

Installing caGrid 1.3 Using the Installer

Download the caGrid 1.3 Installer. The downloaded installer is contained in the file caGrid-installer-1.3.zip.
Unzip the file caGrid-installer-1.3.zip. This creates the directory caGrid-installer-1.3. This documentation refers to this directory as CAGRID_INSTALLER_LOCATION.

From a command prompt, launch the installer using the following command:

 > cd *CAGRID_INSTALLER_LOCATION\\\\* 
 > java -jar caGrid-installer-1.3.jar

Select the I agree to this license checkbox and then click Next.

Select the Install/Configure caGrid Software checkbox. Leave the Install/Configure Grid Service Container checkbox un checked. Then click Next.

The installer detects whether or not you have already installed Ant. It installs or reinstalls it, depending on your installation status. In either case, you must specify the location where you want to install Ant.
The installer detects whether or not you have already installed Globus. It installs or reinstalls it, depending on your installation status. In either case, you must specify the location where you want to install Globus.

The installer asks you for a location to install caGrid. Specify a location to install caGrid and then click Next.

To select a file location that is not in the User's Home directory, Click the Look In: drop down list and select a new starting location.

The installer displays a list of tasks that the installer will perform. Click Next to begin the installation process. At this time the installer downloads, builds, and installs several components. This process takes several minutes.

Once the installer has completed installing all the components, click Next.

The installer prompts you to specify which Grid you want to configure your installation to use. The installer supports configuring caGrid to work out of the box with many community Grid environments. For testing and development purposes, we recommend selecting the Training Grid. If you do not want to configure caGrid to work with an existing Grid you may select that as well. The installer can also be modified to support additional Grids. More information on this can be found in the Add a New Target Grid to the caGrid Installer guide.

The installer shows a summary of the tasks to be completed. Click Next to configure caGrid to use the selected target Grids. This process takes several minutes.

Once the installer has finished configuring caGrid to use the target Grid, click Next. The final screen reminds you to set your ANT_HOME and GLOBUS_LOCATION environment variables. Set these variables immediately and click Finish. Congratulations! You have successfully installed caGrid.

The installer installed caGrid to the directory you specified during installation. From this point forward, this directory will be referred to as CAGRID_HOME.

Step 2: Download and Configure the CSM Service

The Downloads page contains links for downloading the CSM service and administrative interface as either a source or binary distribution.

Installing binary distributions

To install the binary distribution of the CSM Service, download and unzip the caGrid-CSM-Service-1.3.zip file from the Downloads page. The root directory of the service distribution is the csm directory, which will be referred to as CSM_HOME for the remainder of this guide. To install the CSM administrative interface, download and unzip the caGrid-CSM-UI-1.3.zip file from the Downloads page. The root directory of the ui distribution is the csm-ui directory, which will be referred to as CSM_UI_HOME.

Installing source distributions

To install both the CSM Service and administrative interface from the source distribution, download and unzip the caGrid-CSM-src.zip file from the Downloads page. The root directory of the source distribution is caGrid, which will be referred to as CSM_SRC_HOME. The source code for the CSM Service project is located in CSM_SRC_HOME/projects/csm and will be referred to as CSM_HOME. The source code for the administrative interface project is located in CSM_SRC_HOME/projects/csm-ui and will be referred to as CSM_UI_HOME.

Configuring the CSM Service

For both source and binary installations, you must update the database connection information stored in the CSM_HOME/etc/csm.properties file. In most cases you will only need to edit the following properties:

gaards.csm.db.user.id	A MySQL user id that CSM will use to interact with the database. This user should have access to add and remove databases, tables, users, etc. The default and recommended user id is root.
gaards.csm.db.password	The password of the MySQL user specified in gaards.csm.db.user.id
gaards.csm.db.connection.url	Verify that the database connection URL is correct. By default, the URL points to localhost and uses port 3306.

Another copy of the csm.properties file exists: CSM_HOME/test/resources/csm.properties. This copy is used when running the ant test-mysql target to run unit tests. Update this file as well to contain the correct user.id, password and connection.url.

Warning!
The ant test-mysql target will remove the CSM database it is configued to connect to and install a default version for test cases. To avoid removing your CSM database, be sure to configure the gaards.csm.db.connection.url property in the CSM_HOME/test/resources/csm.properties file to point to a different database than the one specified by the gaards.csm.db.connection.url property in your CSM_HOME/etc/csm.properties file.
By default, the gaards.csm.db.connection.url in CSM_HOME/etc/csm.properties to jdbc:mysql://localhost:3306/csm and point the gaards.cs.db.connection.url property in CSM_HOME/test/resources/csm.properties to jdbc:mysql://localhost:3306/csm_test.

Building source distributions

If you installed using the binary distributions, you may skip this step. To build the source distributions, you will need to have Ant version 1.7.0+ installed. To execute a build, run the following commands in a terminal:

 
 > cd CSM_SRC_HOME
 > ant all

This will download all necessary dependencies and build both the CSM Service project and the administrative interface project.

Configuring the CSM admin interface

The CSM administrative interface is an extension of the caGrid GAARDS tool. There are two ways to use the admin interface. You may either launch the tool directly from the UI distribution, or you can update your caGrid GAARDS tool located in $CAGRID_HOME to include the CSM administrative interfaces. Updating the GAARDS tool will rename the Group Management menu item to Access Control. Two additional choices are added to the Access Control menu: Manage Access Control and Manage Privileges. No other changes are made to the interface or functionality of the GAARDS tool. The approach for setting or modifying the target grid differs slightly between the updated GAARDS tool and the csm-ui interface. Refer to the Changing the Target Grid section for instructions related to both approaches.

As mentioned, there are two ways to use the CSM administrative interface. The first option is to launch the admin interface directly from the CSM_UI_HOME directory. If this is your choice, no further configuration is needed at this time and you may proceed to the next step.

The second option is to install the CSM admin interfaces into an existing installation of the caGrid GAARDS tool. The installation process will involve copying a set of files from the CSM_UI_HOME directory to the CAGRID_HOME/projects/gaards-ui directory. To perform the installation, run the following commands in a terminal:

 
> cd CSM_UI_HOME
> ant installToGAARDS

Note that this step requires that a CAGRID_HOME environment variable has been created that points to the location of your caGrid installation.

Adding a CSM Service URL

The default CSM Service URL configured during installation is https://localhost:8443/wsrf/services/CSM*. You may add the URLs of additional CSM services using the GAARDS Preferences interface. If you are not running the CSM Service on the same host as the admin interface, then you should use to process described below to remove localhost from the list of CSM services.

Launch the CSM admin interface. Refer to the Launching the CSM Administration Interface guide for instructions. In the Window menu, click the Preferences item. This will launch the Preferences interface.

preferences interface

In the Preferences tree located in the left pane, expand the Authorization Management subtree. Click on the CSM Service(s) entry. The right pane will update to display the CSM Services preference interface.

CSM services preferences

You should see at least one entry for the default Localhost CSM Service. To add a new CSM Service, enter a short name for the service in the Display Name field. Enter the URL of the service in the Service URL field and optionally add an identity in the Service Identity field. Click the Add button to add the new CSM service to the Services list. You may change the display order of the services by using the Move Up and Move Down buttons. Select a service and clck the Remove button to delete it. Click the Save button at the bottom of the Preferences page when you have finished making changes.


add CSM service URL	updated CSM service list

In the sample screenshot, notice that a new CSM Service URL named Example CSM Service has been added. If you now launch the Application Access Control or Manage Privileges interface, you will see that Example CSM Service has been added to the Service select box.

newly added CSM service

Step 3: Obtain Host Credentials

The CSM Service must be operated as a secure service. In order to run a secure service, the container hosting the service must run with a host credential. A host credential consists of a X.509 certificate and private key. In production environment it is very important that this credential be issued by a certificate authority that your environment trusts. For the purposes of this guide we will provide instructions on how to obtain a host credential from Dorian. Dorian is an open source service framework for issuing PKI credentials and is a trusted certificate authority in many Grid environments. Most target Grids (selected in the last step) are configured with one or more Dorian instances. For the purposes of this guide we will provide documentation on requesting a host credential from the Training Dorian, similiar steps can be used for requesting a host credential from other Dorian instances.

To request a host credential from the Training Dorian, you must have must have an account. Any user may request an account from the Training Dorian. If you have an account with the Training Dorian, please complete the steps below to get a host credential, otherwise click here for directions on requesting an account and then proceed with the steps below:

Launch the GAARDS UI
Login to the Grid.
From the MyAccount menu, select Request a Host Certificate, this will launch the Request a Host Certificate window.
From the Service drop down select the Dorian you wish to request a host certificate from.
In the Host text box, enter the name of the host you are requesting a host certificate for.
Next you must specify the directory on the file system where the host credentials should be written to, this can be done by clicking the Browse button.
Click the Request Certificate button.

Immediately after clicking the Request Certificate button, the UI will submit the host certificate request to Dorian. Upon receiving the request, Dorian will either immediately approve the request or submit the request to administrator for approval. In the case where the request is immediately approved, the host credentials (certificate and private key) will be written to the directory specified. The file containing the certificate will be named THE_HOSTNAME_YOU_ENTERED-cert.pem, the file containing the private key will be named THE_HOSTNAME_YOU_ENTERED-key.pem.

In the case where host certificate request requires approval of an administrator, the file containing the private key will be named THE_HOSTNAME_YOU_ENTERED-key.pem. The host certificate WILL NOT be written since it is not issued until the request is approved. You will need to wait for an administrator to approve your request before proceeding forward. The GAARDS UI provides a means of checking the status of your request. For directions on how to do this click here. Once your request has been approved, verify that the host key and certificate files exist.

Write down the location that the host certificate and private key were written to. These will be needed later to configure your container.
It is also a good idea to make copies of your host key and certificate files and store them in a safe backup location. Should the files ever become lost or corrupted, you can recover them from the backup location.

Step 4: Configure a Secure Container

In this step we will use the caGrid 1.3 Installer to configure a secure web service container for hosting the CSM service. CSM can be deployed to the Tomcat, JBoss, or Globus containers. This guide provides detailed instructions on how to install and configure a secure Tomcat container only. You must supply the installer with the location of the host credentials you created in the last step.

Have a Copy of the .cagrid/certificates Directory
Make sure that you have a copy of the $HOME/.cagrid/certificates directory. There is a bug in the installer that can sometimes corrupt the files in this directory.

After you are finished performing the following steps, check the contents of the $HOME/.cagrid/certificates directory. If the files in this directory have a zero length, they are corrupted. In this case, copy the files from the copy of the $HOME/.cagrid/certificates directory into the directory.

From a command prompt, launch the caGrid Installer:

 > cd <CAGRID_INSTALLER_LOCATION> 
 > java -jar caGrid-installer-1.3.jar

Select the I agree to this license checkbox and then click Next.

Select the Install/Configure Grid Service Container checkbox and then click Next.

Select the Container you to which you want to deploy your service. This guide will use Tomcat. Select the Should this container be secure? checkbox and then click Next.

In the hostname checkbox, enter the hostname of your server. This should match the hostname you used when you created your host credentials. Click Next.

If you plan on using this container to deploy a service that registers to an existing grid, it is important that you use a publicly resolvable DNS name (or static IP). Otherwise, you will need to edit configuration files manually later to correct this.

From the Obtain host credentials method list, select the option that applies to your situation and click Next.

Options:

If you do not yet have credentials for your service, then select Use GAARDS to obtain host credentials.
If you have host credentials that are not in the default location, then select Browse to host credential on the file system
If you have host credentials that are in the default location, then select Host credentials are already installed

Note: Use of the Copy in host credentials manually option is not recommended. Use the Browse to host credential on the file system option instead.

Default credential location:

On Windows, this will be a path like "C:\Documents and Settings\<USERNAME>\.cagrid\certificates".
On Linux/MAC this will be a path like "/Users/YOUR_USERNAME/.cagrid/certificates".

Enter the location of your host certificate into the Certificate text checkbox. Enter the location of your private key into Key text checkbox. Click Next. Note: after this step, verify that your host certificate and private key files exist. Verify that the size of these files is greater than zero. If the filesize is zero for either file, restore it from a backup copy.

The next screen asks where you want to install Tomcat. Enter that location in the Directory text checkbox and click Next.

Avoid Blanks in the Container Path
Do not choose a name or path for the container that contains any blanks. In particular, in a Windows environment, do not put the container under directories such as "Documents and Settings" or "My Documents".

A list of tasks appears that the installer will perform to install and configure Tomcat. Click Next.

Once the installer has completed installing all the components, click Next.

Click Next. The final screen reminds you to set your ANT_HOME, GLOBUS_LOCATION and CATALINA_HOME environment variables. Set these variables immediately and click Finish.
Congratulations! You have successfully installed and configured your Tomcat container.

Step 5: Changing the Target Grid

Both the CSM service and the UI need to be targeted to the correct grid.

Retargeting the Service

The following assumes that the caGrid software is already targeted to the correct grid.

If CAGRID_LOCATION is the root directory of the caGrid distribution, then CAGRID_LOCATION/repository/caGrid/target_grid is a directory that contains directories who name corresponds to a grid that the CSM service could be targeted for. Under the directory whose name corresponds to grid you want the CSM service to work with, is a file named service_urls.properties. If CSM is the root of the CSM service's build directory structure, then copy this service_urls.properties file to the CSM/ext/target_grid directory.

Retargeting the UI

If you wish to use a grid other tthan the training grid, the approach used will depend on whether you are using the updated version of the caGrid GAARDS tool or directly using the csm-ui project for CSM administration.

Using the updated caGrid GAARDS tool

If you are using an updated version of the GAARDS tool, you can change the target grid by following the instructions provided on the How to Change Target Grid wiki page. If the target grid you wish to point to is not included in the list of available grids displayed by running ant configureHelp, you will need to add a set of target grid configuration files to your caGrid 1.3 installation. To accomplish this, follow phase 2 of the Add a New Target Grid to the caGrid Installer guide (phase 1 and phase 3 can be skipped).

Using the csm-ui project

If you are using the csm-ui project located in CSM_UI_HOME to administrate your CSM Service, you must modify configuration files located in the CSM_UI_HOME directory to change the target grid. Open the CSM_UI_HOME/ext/target_grid directory and update the following files. In each file, update the DisplayName property with your target grid's name.

Filename	Description of changes
cds-services-configuration.xml	Change the ServiceURL and ServiceIdentity properties to point your target grid's CDS URL and identity.
dorian-services-configuration.xml	Change the ServiceURL and ServiceIdentity properties to point to your target grid's Dorian URL and identity.
gridgrouper-services-configuration.xml	Change the ServiceURL and ServiceIdentity properties to point to your target grid's Grid Grouper URL and identity.
gts-services-configuration.xml	Change the DisplayName, ServiceURL and ServiceIdentity properties for your target grid's master and slave GTS services.

Step 6: Initialize CSM database or tables (optional)

Earlier we configured the CSM Service to use a database by adding connection info to the csm.properties files. If the CSM database identified in csm.properties has already been installed, you may skip this step and proceed to the next.

However, if no CSM database exists or if you wish to install a fresh instance of the database, execute the following commands from a terminal:

 
> cd CSM_HOME
> ant createMysqlCsmDatabase

This command will drop the database identified in the etc/csm.properties file and install a fresh instance of the CSM database. Note that the fresh instance will not include any administrative users. The next step of this guide will instruct you how to add administrators using the addAdmin ant target.

If an instance of the CSM database already exists, the createMysqlCsmDatabase target will drop the database and reinstall it. All data will be permanently lost. Take care to back up any preexisting data before running the createMysqlCsmDatabase command.

Alternativey, you can use the createMysqlCsmTables ant target to drop and reinstall only the csm tables from the database specified in etc/csm.properties. That is, all other tables in the database will be left intact. Run the following commands from a terminal:

 
> cd CSM_HOME
> ant createMysqlCsmTables

Deciding when to use createMysqlCsmDatabase and createMysqlCsmTables depends on whether or not there are other database tables stored in the database. Since createMysqlCsmDatabase will drop the existing database and recreate it with fresh CSM tables, you should NOT use this command if there are other non-CSM tables in your database. If this is the case, you should use createMysqlCsmTables. This command ONLY drops CSM tables and leaves all other tables in the database alone.

Step 7: Adding a CSM Administrator account

CSM maintains a group of administrators who are granted the ability to manage and review roles, groups, permissions, protection elements, etc. A command line tool exists for bootstrapping CSM with an initial set of administrators. To add a new administrator to CSM, run the following commands from a terminal:

 
> cd CSM_HOME
> ant addAdmin

This will prompt you for the grid identity of an administrator to add. For example:

$ ant addAdmin Buildfile: build.xml checkContribTasksDefined: defineContribTasks: setGlobus: checkGlobus: [echo] Globus: /usr/share/ws-core-4.0.3 defineClasspaths: defineExtendedClasspaths: init: checkValidate: preInit: configure: postInit: addAdmin: [input] Please enter the grid identity for the admin you wish to add: /O=caBIG/OU=caGrid/OU=Training/OU=Dorian/CN=some_username [java] Successfully added /O=caBIG/OU=caGrid/OU=Training/OU=Dorian/CN=some_username as an administrator of the CSM Web Service. BUILD SUCCESSFUL Total time: 2 minutes 47 seconds

When prompted to "Please enter the grid identity for the admin you wish to add:", enter a grid identity. You may run the addAdmin target multiple times to add multiple administrators. Note that as an administrator it is possible to use the CSM admin interface to add other administrators later. For more information on this, refer to the Managing Permissionsguide.

Step 8: Edit Service Metadata

CSM provides service metadata to clients and other services which describes (1) information about the service, (2) operations supported by the service, and (3) information on the organization hosting the service. The information on the organization hosting the service should be edited to reflect your organization. This can be done by editing hostingResearchCenter element and its children in the service metadata file, CSM_HOME/etc/serviceMetadata.xml. Below we show an example of this element, the values of all the attirbutes below should be replaced with the contact information for your organization.

<ns1:hostingResearchCenter><ns53:ResearchCenter displayName="Ohio State University"shortName="OSU"xmlns:ns53="gme://caGrid.caBIG/1.0/gov.nih.nci.cagrid.metadata.common"><ns53:Address country="US"locality="Columbus"postalCode="43210"stateProvince="OH"street1="3190 Graves Hall"street2="333 W. 10th Ave."/><ns53:pointOfContactCollection><ns53:PointOfContact affiliation="OSU"email="John.Doe@osumc.edu"firstName="John"lastName="Doe"phoneNumber="(555) 555-5555"role="Administrator"/></ns53:pointOfContactCollection></ns53:ResearchCenter></ns1:hostingResearchCenter>

Step 9: Deploy CSM Service to secure container

We have completed configuring the CSM Service and the secure Tomcat container that the service will be deployed to. We are ready to deploy the service. To deploy to a secure Tomcat container, run the following command from a terminal:

 
> cd CSM_HOME
> ant deployTomcat

If you chose to use a JBoss container, CSM can be deployed by running the following command from a terminal:

 
> cd CSM_HOME
> ant deployJBoss

Although the installer does not support configuring a secure Globus container, CSM can be deployed to a secure Globus container by running the following command from a terminal:

 
> cd CSM_HOME
> ant deployGlobus

No matter which container you choose you should see a significant amount of output to the screen. If the deployment is successful you should see the words "BUILD SUCCESSFUL" will be displayed.

Starting a secure Tomcat container

Once you have deployed the CSM Service, we need to start the container. For example, run the following commands to start a secure Tomcat container:

 
> cd $CATALINA_HOME/bin
> ./startup.sh

Refer to your container's documentation for more information about starting, stopping and administrating the container.

Step 10: Verifying the Installation

The CSM Service has been installed, configured and deployed to a running secure container. We can now use the CSM admin interface to interact with the service and verify that it was correctly installed. Additionally, we can execute the CSM Service JUnit tests for further validation.

Validation using CSM admin interface

During the installation process, we bootstrapped the CSM Service with at least one admin user account. This process not only created a CSM user, but also created an application, protection element, and protection group each named CSM Web Service. The process also created a role named Administrator, a group named CSM Web Service Administrators, a privilege named ADMIN, and a permission that links the CSM Web Service Administrators group to the CSM Web Service protection group and Administrator role. We will use the CSM admin interface to view each of these to verify the installation was successful.

Verify ADMIN Privilege

First, launch the CSM admin interface using instructions from the Launch Admin Interface guide. Login to the tool using an account that has been configured as a CSM administrator. From the Access Control menu, choose Manage Privileges. The Manage Privileges interface will appear. Specify your CSM service using the Service select box and select your CSM admin credential from the Credential select box. Click the Search button. The Privileges search results box should display a privilege named ADMIN. Double click on ADMIN to view its details the Modify Privilege interface. Close the Modify Privilege and Manage Privilege interfaces.


launch manage privileges	view ADMIN privilege

Verify CSM application

Next, from the Access Control menu choose Manage Access Control to launch the Application Access Control interface. Again, specify your CSM service and admin credential in the appropriate select boxes. Click the Search button and you should see an application named CSM Web Service in the Applications search results box. Double click the CSM Web Service result to launch the Access Control Management interface.


manage access control interface	launch access control management

Verify CSM Web Service protection element

By default, the Protection Elements tab will be displayed in the Access Control Management interface. Without entering any values in the Search for Protection Elements search fields, click the Search button. You should see one result named CSM Web Service listed in the Protection Elements search results box. Double click the CSM Web Service protection element to launch the Edit Protection Element interface. Notice that the Attribute Name, Attribute Value and Type fields are empty. Close the Edit Protection Element interface.


protection element search results	edit protection element

Verify CSM Web Service protection group

Click on the Protection Groups tab. Without entering anything in the Protection Group Search box, click the Search button. In the Protection Groups search results box, you should see a group named CSM Web Service listed under the Protection Groups root group. Click on the CSM Web Service group in the search results to populate the Protection Elements in Protection Group window on the left side of the interface. You should see that the CSM Web Service protection element has been added to the CSM Web Service protection group. Click on the Modify button in the lower left corner of the interface to launch the Edit Protection Group interface. After viewing the protection group's details, close the Edit Protection Group interface.


protection group tab	edit protection group

Verify Administrator Role

Click on the Roles tab. Without entering anything in the Role Search input box, click the Search button. You should see a single role named Administrator displayed in the Roles search result box. Click on the Administrator role to display its details in the Role window on the right side of the interface. You should see that the Privileges in Role box includes the ADMIN privilege. Depending on how the CSM database was originally installed, you may see more privileges shown in theAvailable Roles box that are shown in the above illustration.

roles tab

Verify CSM Web Service Administrators Group

Click on the Groups tab. Without entering anything in the Group Search input box, click the Search button. You should see a single group named CSM Web Service Administrators listed in the Groups search result box. Click on the CSM Web Service Administrators group to display its details in the details window to the right. This should be a local group. You should see the list of admin users you set up using the addAdmin command in the Members box in the lower right corner of the interface. In the sample screenshot, the only CSM admin user entered is /O=caBIG/OU=caGrid/OU=Training/OU=Dorian/CN=kgasper.

groups tab

Verify Permission

Click on the Permissions tab. Select Group from the Search Type select box. Click on the Find button to the right of the Group input box. The Select Group interface will appear. Without entering anything in the Group Name field, click the Search button. You should see the CSM Web Administrators group in the Groups search result box. Click on CSM Web Administrators to highlight it and click the Select button. The Group input box should now contain CSM Web Administrators. Click on the Search button. You should see a single permission listed in the Permissions for CSM Web Administrators search results box. Click it to highlight it and click the Modify button to launch the Modify Permission interface. You should see CSM Web Administrators listed in the Group input box, CSM Web Service listed in the Protection Group input box, and Administrator listed in the Granted Roles box. Close the Modify Permission interface.


find group	permission search results

modify permission

Running CSM JUnit Tests

The CSM Service project is distributed with a suite of JUnit tests that may be used to validate your installation. In order to run the JUnit tests, you must have Apache Ant version 1.7+ installed. You must also configure the CSM_HOME/test/resources/csm.properties as explained in the Configuring the CSM Service section.

Make sure that the CSM_HOME/test/resources/csm.properties gaards.csm.db.connection.url property specifies a different database name than the one specified in CSM_HOME/etc/csm.properties.

To execute the CSM Service JUnit tests, run the following commands in a terminal:

 
> cd CSM_HOME
> ant test-mysql

It will take some time for the tests to finish execution. If the tests were successful, you should see something similar to the following:

test-mysql:
     [echo] Test results dir: test/logs/junit
    [junit] Running org.cagrid.gaards.csm.service.TestCSM
    [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 215.418 sec
    [junit] Running org.cagrid.gaards.csm.service.TestRemoteGroupManager
    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 30.293 sec

BUILD SUCCESSFUL
Total time: 4 minutes 7 seconds

CSM