Skip to content
Snippets Groups Projects
Commit 10df12f5 authored by Nicholas Terranova's avatar Nicholas Terranova
Browse files

fixed README.md, adding links

parent 966825b6
No related branches found
No related tags found
1 merge request!1Resolve "Setup test proxy certificates and basic VOMS module testing"
...@@ -6,23 +6,9 @@ Setup and files to test the *ngx\_http\_voms\_module* are contained in the `t` f ...@@ -6,23 +6,9 @@ Setup and files to test the *ngx\_http\_voms\_module* are contained in the `t` f
### Test fixture setup ### Test fixture setup
Proxy certificates are in the `certs` folder: Proxy certificates are in the `certs` folder (see [README.md](certs/README.md) for further details). Trust-anchors (e.g. igi-test-ca.pem) are contained in the `trust-anchors` folder. Nginx server certificate and key are nginx\_voms\_example.cert.pem and nginx\_voms\_example\_key.pem, respectively, and they are in the `certs` folder.
* 0.pem: long-lived proxy certificate, without Attribute Certificate (AC); To perform correctly the VOMS AC validation, a \*.lsc or \*.pem file is needed, see [VOMS client 3.3.0 User Guide](http://italiangrid.github.io/voms/documentation/voms-clients-guide/3.0.3/) for further details. The *voms.example.lsc* can be found in `vomsdir/test.vo`.
* 1.pem: long-lived proxy certificate, with an expired AC;
* 2.pem: expired proxy certificate.
Proxy certificates are generated using [VOMS client 3.3.0](http://italiangrid.github.io/voms/documentation/voms-clients-guide/3.0.3/).
The following command is used:
VOMS_CLIENTS_JAVA_OPTIONS="-Dvoms.fake.vo=test.vo -Dvoms.fake=true -Dvoms.fake.aaCert=<path_to_cert>/voms_example.cert.pem -Dvoms.fake.aaKey=<path_to_key>/voms_example.key.pem" voms-proxy-init3 -voms test.vo -cert <path_to_test0>/test0.p12 --valid <validity>
*voms\_example.cert.pem* and *voms\_example.ket.pem* can be found in the `certs` folder.
To perform correctly the VOMS AC validation, a \*.lsc or \*.pem file is needed in `/etc/grid-security/vomsdir`, see [VOMS client 3.3.0 User Guide](http://italiangrid.github.io/voms/documentation/voms-clients-guide/3.0.3/) for further details. An example of *voms.example.lsc* can be found in `vomsdir/test.vo`.
Trust-anchors (igi-test-ca.pem) are contained in the `trust-anchors` folder. Nginx server certificate and key (nginx\_voms\_example.cert.pem and nginx\_voms\_example\_key.pem) are in the `certs` folder.
### Running Tests ### Running Tests
...@@ -30,8 +16,7 @@ To run the tests made available in the `t` folder just type ...@@ -30,8 +16,7 @@ To run the tests made available in the `t` folder just type
prove -v prove -v
Using the docker image provided to exploit Openresty in the Storm2 project (see [README.md](../README.md) for further details):
Using the docker image provided to exploit Openresty in the Storm2 project:
cp -r t /tmp cp -r t /tmp
cd /tmp cd /tmp
......
# Certificates for ngx\_http\_voms\_module Testing
Proxy certificates are generated using [VOMS client 3.3.0](http://italiangrid.github.io/voms/documentation/voms-clients-guide/3.0.3/):
* 0.pem: long-lived proxy certificate, without Attribute Certificate (AC);
* 1.pem: long-lived proxy certificate, with an expired AC;
* 2.pem: expired proxy certificate.
To obtain such certificates the following command is used:
VOMS_CLIENTS_JAVA_OPTIONS="-Dvoms.fake.vo=test.vo -Dvoms.fake=true -Dvoms.fake.aaCert=<path_to_cert>/voms_example.cert.pem -Dvoms.fake.aaKey=<path_to_key>/voms_example.key.pem" voms-proxy-init3 -voms test.vo -cert <path_to_test0>/test0.p12 --valid <validity>
*voms\_example.cert.pem* and *voms\_example.ket.pem* can be found in the `certs` folder.
To perform correctly the VOMS AC validation, a \*.lsc or \*.pem file is needed in `/etc/grid-security/vomsdir`, see [VOMS client 3.3.0 User Guide](http://italiangrid.github.io/voms/documentation/voms-clients-guide/3.0.3/) for further details. An example of *voms.example.lsc* can be found in `vomsdir/test.vo`.
Nginx server certificate and key are nginx\_voms\_example.cert.pem and nginx\_voms\_example\_key.pem.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment