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