3.2 KiB
Running Keystone in HTTPD
Warning
Running Keystone under HTTPD in the recommended (and tested)
configuration does not support the use of
Transfer-Encoding: chunked
. This is due to a limitation
with the WSGI spec and the implementation used by mod_wsgi
.
It is recommended that all clients assume Keystone will not support
Transfer-Encoding: chunked
.
Files
Copy the httpd/wsgi-keystone.conf
sample configuration
file to the appropriate location for your Apache server, on
Debian/Ubuntu systems it is:
/etc/apache2/sites-available/wsgi-keystone.conf
On Red Hat based systems it is:
/etc/httpd/conf.d/wsgi-keystone.conf
Update the file to match your system configuration. Note the following:
- Make sure the correct log directory is used. Some distributions put
httpd server logs in the
apache2
directory and some in thehttpd
directory. - Enable TLS by supplying the correct certificates.
Keystone's primary configuration file
(etc/keystone.conf
) and the PasteDeploy configuration file
(etc/keystone-paste.ini
) must be readable to HTTPD in one
of the default locations described in configuration
.
Enable the site by creating a symlink from the file in
sites-available
to sites-enabled
, for example,
on Debian/Ubuntu systems (not required on Red Hat based systems):
ln -s /etc/apache2/sites-available/keystone.conf /etc/apache2/sites-enabled/
Restart Apache to have it start serving keystone.
Access Control
If you are running with Linux kernel security module enabled (for example SELinux or AppArmor) make sure that the file has the appropriate context to access the linked file.
Keystone Configuration
Make sure that when using a token format that requires persistence, you use a token persistence driver that can be shared between processes. The SQL and memcached token persistence drivers provided with keystone can be shared between processes.
Warning
The KVS (kvs
) token persistence driver cannot be shared
between processes so must not be used when running keystone under HTTPD
(the tokens will not be shared between the processes of the server and
validation will fail).
For SQL, in /etc/keystone/keystone.conf
set:
[token]
driver = sql
For memcached, in /etc/keystone/keystone.conf
set:
[token]
driver = memcache
All servers that are storing tokens need a shared backend. This means that either all servers use the same database server or use a common memcached pool.