Guidlines for certifying Trustmanager

For some background on Trustmanager go:

Basically trustmanager is a server side SSL connection handler which handles connections with grid certificates and proxies. It also has a client side library to form those connections.

The testplan (currently has the description of the tests. Basically the test are separated to three parts. Server side certificate tests, server side API tests and client side API tests. NB! The API test are currently done using test programs shipped with Trustmanager. This is not ideal since they might not catch interface changes/bugs since they happen to be broken in the same build as Trustmanager. However, they are by far the simplest to use, and they are used because of time constraints. Future certifier (yes you), you can gladly write new API tests :).

Server side certificate tests: These test use openssl's s_client to connect to the server with different types of certificates. Some connections should fail and some should succeed. These tests are and

Server side API tests: These use wget to get a page from a server test webapplet. This page contains the information trustmanager reports about the connecting client certificates. The information is parsed and checked against the certificates used. NB! If the webapp has changed you might need to revise the result parsing in the tests! These tests are in

Client side api tests: These test use a test client program shipped with trustmanager to connect to the test webservice interface with different types of client certificates, and server certificates. NB! Since the java command always returns 0, the test parse the output of the client. The checks might need to be revised if the output has changed. The tests are and

Since the tests use a lot of different certificate types, the certificate generation scripts from are used. This is a requirement to run the tests. More info in the setup section.

For now these tests are run with tomcat5 and SLC4, but it they should "almost" work on tomcat6. You need to do some configuration redifinitions in the beginnig of a few files (grep tomcat5 * should tell you where).

These tests need to be run as root, since they play with /etc/grid-security/certificates and tomcat restarting.

NB! For the same certificate playing reasons, all tests should be run on the same machine where trustmanager is installed! Even the client ones.


Since the trustmanger is used by many node types, the certification is split into these parts.

1) Do the test setup (described soon) 2) Run the tests included here 3) For each node type, install it and check that the connection management works with the new Trustmanger, or ask someone to do it. The node types do not need to be thoroughly tested, only the SSL connection handling part.


The setup part is a bit tricky, but after that the tests should be relatively straightforward.

To start install a mahcine with the patches and other necessary stuff incl. tomcat, certificates, glite-security-voms-clients, glite-version and yaim-core,

Then you need to check out and run bin/ --all --voms with a destination directory where they are created. This might take a few minutes. NB! This script creates proxy certs, so you need to recreate the certificates if certification takes over 8 ours. This is no problem, you just need to clean the directory, and run it and the (mentioned later) again.

Then you need to run
/opt/glite/yaim/bin/yaim  -r -s site-info.def  -f config_secure_tomcat
/opt/glite/yaim/bin/yaim  -r -s site-info.def  -f config_vomses

This should configure tomcat and trustmanager to the needed degree. You need to make one change in /etc/tomcat5/server.xml, add the line

This is so that the server can run with expired certificates too, and is needed for the client tests.

The Trustmanager RPM contains glite-security-trustmanager.war which should be deployed under the tomcat webapps dir (copy it to /var/lib/tomcat5/webapps).

After this has been deployed (tomcat started), and the war has been unpacked, you need to compile the client test code too. To do this, check out and compile the test app against the deployed war to have all necessary libs. So basically

for f in /var/lib/tomcat5/webapps/glite-security-trustmanager/WEB-INF/lib/*.jar  ; do 

cd thediryoucheckedthecodeto/test/src
javac org/glite/security/trustmanager/axis/
This should compile the client against the currect Trustmanager.

Finally, run --certdir test_utils_cert_place. This sets up the certificates for the tests. Note! The creates an one hour CRL (to later test CRL expiration), so if you're not done before that, just rerun the same command.


The tests are split to three parts. The recommended running order is:

All commands take arguments, run them with --help to display. The commmand also have some definable variables in the beginning of the file, these should work with the default values.

All tests report if they pass or fail. Remeber that some of the test rely on parsing the output to check the outcome. If tests fail it might be because the output format has changed. Check this first.

After running these tests you need to wait for an hour for the CRL to expire. You can run to check when they can be run. When the CRL has expired run:

Note that since the tests play around with the certificates that are being used, if you Ctrl-C in the middle of a test you may leave the certificates in an unspecified state.

-- KalleHapponen - 26 Jun 2009

Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r5 - 2009-11-17 - unknown
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback