Monty Taylor f8ba5af130 Align with project configs.

* docs in doc/ rather than docs/
* write out changelog from git
* freeze requirements file

Change-Id: If28d5414f7b2747fd6835546c45e1acfac8a3563

2012-03-01 11:42:42 -08:00

3.5 KiB

Raw Blame History

x.509 Client Authentication

Purpose

Allows the Keystone middleware to authenticate itself with the Keystone server via an x.509 client certificate. Both Service API and Admin API may be secured with this feature.

Certificates

The following types of certificates are required. A set of certficates is provided in the examples/ssl directory with the Keystone distribution for testing. Here is the description of each of them and their purpose:

ca.pem: Certificate Authority chain to validate against.
keystone.pem: Public certificate for Keystone server.
middleware-key.pem: Public and private certificate for Keystone middleware.
cakey.pem: Private key for the CA.
keystonekey.pem: Private key for the Keystone server.

Note that you may choose whatever names you want for these certificates, or combine the public/private keys in the same file if you wish. These certificates are just provided as an example.

Configuration

By default, the Keystone server does not use SSL. To enable SSL with client authentication, modify the etc/keystone.conf file accordingly:

To enable SSL for Service API:
```
service_ssl = True
```
To enable SSL for Admin API:
```
admin_ssl = True
```
To enable SSL client authentication:
```
cert_required = True
```
Set the location of the Keystone certificate file (example):
```
certfile = /etc/keystone/ca/certs/keystone.pem
```
Set the location of the Keystone private file (example):
```
keyfile = /etc/keystone/ca/private/keystonekey.pem
```

Set the location of the CA chain:

ca_certs = /etc/keystone/ca/certs/ca.pem

Middleware

Add the following to your middleware configuration to support x.509 client authentication. If cert_required is set to False on the keystone server, the certfile and keyfile parameters in steps 3) and 4) may be commented out.

Specify 'https' as the auth_protocol:
```
auth_protocol = https
```
Modify the protocol in 'auth_uri' to be 'https' as well, if the service API is configured for SSL:
```
auth_uri = https://localhost:5000/
```
Set the location of the middleware certificate file (example):
```
certfile = /etc/keystone/ca/certs/middleware-key.pem
```
Set the location of the Keystone private file (example):
```
keyfile = /etc/keystone/ca/certs/middleware-key.pem
```

For an example, take a look at the echo.ini middleware configuration for the 'echo' example service in the examples/echo directory.

Testing

You can test out how it works by using the echo example service in the examples/echo directory and the certficates included in the examples/ssl directory. Invoke the echo_client.py with the path to the client certificate:

python echo_client.py -s <path to client certificate>

3.5 KiB Raw Blame History