DILIGENT Gridsphere and Portal Security patch
In order to communicate with the VOMS the DILIGENT portal requires an additional component (named in the following "VOMS servlet"). It has to be deployed independently and in a container DIFFERENT from that hosting the DILIGENT portal. This means that you have to install TWO tomcat containers. The first one (a standard tomcat 5.5.20) will host the VOMS Servlet, while the second (a patched version of tomcat 5.5.20) will hosts the DILIGENT-Gridsphere portal.
Configure properly your host
There is a number of preliminary steps you have to perform to install the portal. First of all the host requires a DHN installation. The DHN must be installed and properly configured as described DHN installation and DHN configure security, but it does not requires to be started. The reason to have it installed is that DILIGENT portlets requires to access and use libraries and configuration files of the local DHN.
Please remove servlet.jar and naming-*.jar from your $GLOBUS_LOCATION/lib in the end of this installation.
Secondly you need to properly configure security for the node as described in the [How To Configure DHN Security] page. Lastly you need to check the existence of voms-proxy-init command in your host. If not, you can find the necessary rpm on BSCW at /DILIGENT Members / Work packages / Work packages 1x / WP 1.2 / Security / voms-proxy-init rpm.
Install a standard tomcat container
To host the VOMS servlet you need a separate installation of the tomcat 5.5.20 container. We suggest to install it using a separate user, to avoid errors in the environment settings (i.e. with the $CATALINA_HOME variable). Detailed information about tomcat installation can be found in the RUNNING.txt file inside the distribution package.
Create servlet credentials
To succesfully contact the VOMS service the VOMS servlet needs valid credentials, registered in the VOMS it needs to contact and associated to the VO-Admin role. This is required as the servlet needs to create users, groups and roles in the VOMS service.
These credentials needs to be converted in a PKCS12 format to be loaded by the servlet. Starting from valid credentials in PEM format (usually host credentials can be used for this purpose) you need to issue this command to convert it to PKCS12 format:
openssl pkcs12 -export -in <path_to_the_hostcert.pem> -inkey <path_to_the_hostkey.pem> -out <output_file.p12>
This will create a new (password protected) file containing both the certificate and the private key. We'll use the file and the password later in the service configuration.
The servlet also needs to trust the certificate of the VOMS service, to this purpose a Java truststore containing the VOMS certificate must be created. To create one you can simply issue this command:
keytool -import -alias <name> -file <path_to_VOMS_cert.pem> -keystore <path_to_your_trustStore_file>
The alias is simply a string to identify the certificate you're importing in the truststore. If the trsustore file does not exists it will be created. For instance if you want to import the grids13.eng.it certificate in the trsutstore you have to issue:
keytool -import -alias grids13 -file /etc/grid-security/vomsdir/grids03.eng.it-diligent.pem -keystore certs/VOMSServlet.trustStore
To list certificates stored in the trustStore:
keytool -list -v -keystore <path_to_your_trustStore_file>
Here you can find further information to manage a trustStore.
Install and configure the VOMS servlet
Once deployed the servlet needs to be configures to point to the right VOMS installation. You can do this editing the $CATALINA_HOME/webapps/VOMSServlet/WEB-INF/web.xml file. Following parameters must be set:
<!-- the host name of the VOMS Admin interface --> <init-param> <param-name>hostName</param-name> <param-value>https://grids13.eng.it:8443/voms/diligent/services/VOMSAdmin</param-value> </init-param> <!-- the pcks12 certificate --> <init-param> <param-name>keyStore</param-name> <param-value>output_file.p12</param-value> </init-param> <!-- the keystore type --> <init-param> <param-name>keyStoreType</param-name> <param-value>PKCS12</param-value> </init-param> <!-- the password of the specified keyStore --> <init-param> <param-name>keyStorePassword</param-name> <param-value>pkcs12_password</param-value> </init-param> <!-- the path to a trustStore --> <init-param> <param-name>trustStore</param-name> <param-value>path_to_your_trustStore_file</param-value> </init-param> <!-- the password of the specified keyStore --> <init-param> <param-name>trustStorePassword</param-name> <param-value>truststore_password</param-value> </init-param> <!-- the truststore type --> <init-param> <param-name>trustStoreType</param-name> <param-value>JKS</param-value> </init-param>
At this point the servlet should be properly configured. Then start the tomcat container.
In order to enable interoperation between the VOMS servlet and the VOMS service the certificate used by the servlet (that in pkcs12 format) must be registrered in the VOMS and associated to the VO-Admin role. This is required as the servlet needs to create users, groups and roles in the VOMS service.
Please be carefull that the user's CLASSPATH that is running the container don't import GLOBUS_LOCATION: otherwise you could have an exception like that org.apache.axis.types.URI$MalformedURIException: Cannot initialize URI with empty parameters.
Install the Gridsphere portal
To properly install the DILIGENT portal you need to use patched version of tomcat and Gridsphere. You can download them from the DILIGENT BuildReport following these links:
First of all untar the DILIGENT-Gridsphere package in a local directory (in the following named GRIDSPHERE_LOCATION). Then you have to configure a number of parameters to enable interoperation between the portal and the VOMS servlet. To do this editing the file GRIDSPHERE_LOCATION/webapps/gridsphere/WEB-INF/classes/PortalSecurity.properties.
In particular you have to specify parameters of the MyProxy service you want to use:
and an existing directory in your filesystem where to store temporary generated proxy certificates
Then you have to specify a number of information needed to communicate with the VOMSServlet:
SERVLET_HOST=localhost SERVLET_PORT=port_of_your_container SERVLET_PATH=path_to_the_VOMS_servlet SERVLET_PROTOCOL=http
These parameters must point to the servlt you deployed in the first part of this installation. An example of configuration is given below:
E.g.: SERVLET_HOST=grids15.eng.it SERVLET_PORT=8080 SERVLET_PATH=/VOMSServlet/VOMSServlet SERVLET_PROTOCOL=http
You have then to follows standard steps to install the Gridsphere portal as described here. Instead of download the tomcat core container from the website use the patched one. Please notice that the additional packages required for tomcat can be downloaded following these links:
Patch the Tomcat installation
Your Tomcat 5.5.20 instance needs a particular configuration to run correctly the DILIGENT-Gridsphere portal:
You have to set two environment variables:
* GLOBUS_LOCATION * CATALINA_OPTS=-DGLOBUS_LOCATION=$GLOBUS_LOCATION
and edit the setclasspath.sh (or setclasspath.bat) file in the $CATALINA_HOME/bin as following:
# Set standard CLASSPATH if [ "$1" = "debug" -o "$1" = "javac" ] ; then CLASSPATH="$CLASSPATH":"$JAVA_HOME"/lib/tools.jar fi
This concludes the installation of the DILIGENT-Gridsphere portal. You have just to startup the tomcat container.
The portal will be fully operational only once the DILIGENT portlets bundle has been deployed. Refers to the Gridsphere Bundle Deployment to deploy the bundle containing all DILIGENT portlets.