Skip to content
Snippets Groups Projects
README.md 2.67 KiB
Newer Older
Francesco Giacomini's avatar
Francesco Giacomini committed
# `ngx_http_voms_module` Testing 
Nicholas Terranova's avatar
Nicholas Terranova committed

## Description

Francesco Giacomini's avatar
Francesco Giacomini committed
Setup and files to test the *ngx_http_voms_module* are contained in the `t` folder. The [Openresty data-driven testsuite](https://openresty.gitbooks.io/programming-openresty/content/testing/) has been adopted for testing.
Nicholas Terranova's avatar
Nicholas Terranova committed
### Test fixture setup 
Nicholas Terranova's avatar
Nicholas Terranova committed

Francesco Giacomini's avatar
Francesco Giacomini committed
All the certificates and proxy certificates used in the tests are in the [`certs`](certs) folder (see that [README](certs/README.md) for further details), while trust-anchors (e.g. igi-test-ca.pem) are in the [`trust-anchors`](trust-anchors) folder.
Francesco Giacomini's avatar
Francesco Giacomini committed
`vomses` is the _vomses_ file needed for the generation of proxy certificates.
Nicholas Terranova's avatar
Nicholas Terranova committed

Francesco Giacomini's avatar
Francesco Giacomini committed
The LSC file `voms.example.lsc`, needed to perform correctly the VOMS AC validation, is in the [`vomsdir/test.vo`](vomsdir/test.vo) folder.
Nicholas Terranova's avatar
Nicholas Terranova committed

### Running Tests

To run the tests made available in `t` just type
Nicholas Terranova's avatar
Nicholas Terranova committed

Francesco Giacomini's avatar
Francesco Giacomini committed
```shell
$ prove -v 
```
Nicholas Terranova's avatar
Nicholas Terranova committed

from `t`' s parent directory.

Francesco Giacomini's avatar
Francesco Giacomini committed
The `prove` command creates a directory called `servroot` in `t`, so if the `t` folder is accessible read-only, for
example in a docker container, just make a copy somewhere else and run the tests from there:
```shell
Francesco Giacomini's avatar
Francesco Giacomini committed
cp -r t /tmp
cd /tmp
prove -v
Note: the alert below is unavoidable, but it doesn't affect the tests.
```
[alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
```

Francesco Giacomini's avatar
Francesco Giacomini committed
### Testing directly the Nginx server
Francesco Giacomini's avatar
Francesco Giacomini committed
You can reuse the config file `t/servroot/conf/nginx.conf` produced by `test::Nginx`, which contains something like
http {
    client_body_temp_path /tmp/client_temp;
    proxy_temp_path       /tmp/proxy_temp_path;
    fastcgi_temp_path     /tmp/fastcgi_temp;
    uwsgi_temp_path       /tmp/uwsgi_temp;
    scgi_temp_path        /tmp/scgi_temp;
    server {
        listen 8443 ssl;
        server_name     nginx-voms.example;
        ssl_certificate ../../certs/nginx_voms_example.cert.pem;
        ssl_certificate_key ./certs/nginx_voms_example.key.pem;
        ssl_client_certificate ./trust-anchors/igi-test-ca.pem;
        ssl_verify_depth 10;
        ssl_verify_client on;
        location = / {
            echo user: $voms_user;
        }
You may want to change the configuration so that the log goes to standard output instead of to a log file:
```
server {
    error_log /dev/stdout debug;
    ...
```
Francesco Giacomini's avatar
Francesco Giacomini committed

```shell
$ nginx -c conf/nginx.conf -p t/servroot/ -elogs/error.log
Francesco Giacomini's avatar
Francesco Giacomini committed
Modify (as root) `/etc/hosts` so that `nginx-voms.example` is an alias for `localhost`:

```
127.0.0.1	localhost nginx-voms.example
```

Francesco Giacomini's avatar
Francesco Giacomini committed
Then run for example `curl`, calling directly the HTTPS endpoint:

```shell
$ curl https://nginx-voms.example:8443 --cert t/certs/3.pem --capath t/trust-anchors --cacert t/certs/3.cert.pem