Certification report patch 4639
Author(s): John White
Patch:
https://savannah.cern.ch/patch/index.php?4639
Outcome:
Certified
Test setup
Installed gLite Argus and gLite UI nodes on VM vtb-generic-91.cern.ch and gLite-Argus on vtb-generic-54.cern.ch
The output of the automatic installation and configuration can be found
here.
wget http://etics-repository.cern.ch/repository/download/volatile/tschopp/org.glite/org.glite.authz.pep-c-cli/2.0.0/sl5_x86_64_gcc412/glite-authz-pep-c-cli-2.0.0-0.sl5.x86_64.rpm
wget
http://etics-repository.cern.ch/repository/download/registered/org.glite/org.glite.authz.pep-api-c/2.0.1/sl5_x86_64_gcc412/glite-authz-pep-api-c-2.0.1-1.sl5.x86_64.rpm
rpm -ivh glite-authz-pep-c-cli-2.0.0-0.sl5.x86_64.rpm
rpm -ivh glite-authz-pep-api-c-2.0.1-1.sl5.x86_64.rpm
ldconfig
On vtb-generic-91.cern.ch a test user (user1) was created and cert/key assigned.
The PAP configuration was created according to
org.glite.testsuites.ctb/Argus/PEPJ/manual/README
and the policy{1:3} copied to vtb-generic-54.cern.ch as per the aforementioned instructions.
The PAP configuration was run on vtb-generic-54.cern.ch.
Certification
After the setup, the certification test script was simply run on the glite-UI machine. The output of the test is attached. All tests passed, no problems found. See below:
[user1@vtb-generic-91 tests]$ /opt/glite/bin/pepcli -V
argus-pepcli/2.0.0 [glite-authz-pep-api-c/2.0.1 (libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5)]
./pepc-tests.sh -s vtb-generic-54.cern.ch
argus-pepcli/2.0.0 [glite-authz-pep-api-c/2.0.1 (libcurl/7.15.5
OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5)]
#pep-c certification test# Retrieving a proxy certificate
#pep-c certification test# Testing basic policy with voms based allow clause
#pep-c certification test# Succesfully got mapping
#pep-c certification test# Testing basic policy with subject based allow clause
#pep-c certification test# Succesfully got mapping
#pep-c certification test# Testing basic policy with subject based deny clause
#pep-c certification test# Did nor receive mapping, which is correct behaviour.
#pep-c certification test# Testing nonexisting policy
#pep-c certification test# Did nor receive mapping, which is correct behaviour.
#pep-c certification test# Testing against a fake host
#pep-c certification test# Fake host error not reported.
#pep-c certification test# Reported error for nonexisting Host
#pep-c certification test# Testing without a certificate
#pep-c certification test# Got error message for missing file
#pep-c certification test# Testing without a key
#pep-c certification test# Got error message for missing file
#pep-c certification test# Testing without a proxy
#pep-c certification test# Got error message for missing file
#pep-c certification test# Retrieving short proxy, to test with an expried proxy
#pep-c certification test# Testing with an expired proxy
#pep-c certification test# Got error message for expired proxy file
= test PASSED =
Here
is the testing script used above.
--
JohnWhite - 14-Feb-2011