459f078d0c
Divided the keystone docs into four categories, depending upon the usage criteria: general information (which will be common for all), developer documentation, user documantation and operator documentation. Change-Id: I2f5dd41acd9874739accc54c4f4fd69460b58334
97 lines
3.3 KiB
ReStructuredText
97 lines
3.3 KiB
ReStructuredText
:orphan:
|
|
|
|
..
|
|
Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
not use this file except in compliance with the License. You may obtain
|
|
a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
License for the specific language governing permissions and limitations
|
|
under the License.
|
|
|
|
Setup OpenID Connect
|
|
====================
|
|
|
|
----------------------------
|
|
Configuring mod_auth_openidc
|
|
----------------------------
|
|
|
|
Federate Keystone (SP) and an external IdP using OpenID Connect (`mod_auth_openidc`_)
|
|
|
|
.. _`mod_auth_openidc`: https://github.com/pingidentity/mod_auth_openidc
|
|
|
|
To install `mod_auth_openidc` on Ubuntu, perform the following:
|
|
|
|
.. code-block:: bash
|
|
|
|
$ sudo apt-get install libapache2-mod-auth-openidc
|
|
|
|
This module is available for other distributions (Fedora/CentOS/Red Hat) from:
|
|
https://github.com/pingidentity/mod_auth_openidc/releases
|
|
|
|
Enable the auth_openidc module:
|
|
|
|
.. code-block:: bash
|
|
|
|
$ sudo a2enmod auth_openidc
|
|
|
|
In the keystone vhost file, locate the virtual host entry and add the following
|
|
entries for OpenID Connect:
|
|
|
|
.. code-block:: none
|
|
|
|
<VirtualHost *:5000>
|
|
|
|
...
|
|
|
|
OIDCClaimPrefix "OIDC-"
|
|
OIDCResponseType "id_token"
|
|
OIDCScope "openid email profile"
|
|
OIDCProviderMetadataURL <url_of_provider_metadata>
|
|
OIDCClientID <openid_client_id>
|
|
OIDCClientSecret <openid_client_secret>
|
|
OIDCCryptoPassphrase openstack
|
|
OIDCRedirectURI http://localhost:5000/v3/OS-FEDERATION/identity_providers/<idp_id>/protocols/openid/auth
|
|
|
|
<LocationMatch /v3/OS-FEDERATION/identity_providers/.*?/protocols/openid/auth>
|
|
AuthType openid-connect
|
|
Require valid-user
|
|
LogLevel debug
|
|
</LocationMatch>
|
|
</VirtualHost>
|
|
|
|
Note an example of an `OIDCProviderMetadataURL` instance is: https://accounts.google.com/.well-known/openid-configuration
|
|
If not using `OIDCProviderMetadataURL`, then the following attributes
|
|
must be specified: `OIDCProviderIssuer`, `OIDCProviderAuthorizationEndpoint`,
|
|
`OIDCProviderTokenEndpoint`, `OIDCProviderTokenEndpointAuth`,
|
|
`OIDCProviderUserInfoEndpoint`, and `OIDCProviderJwksUri`
|
|
|
|
Note, if using a mod_wsgi version less than 4.3.0, then the `OIDCClaimPrefix`
|
|
must be specified to have only alphanumerics or a dash ("-"). This is because
|
|
mod_wsgi blocks headers that do not fit this criteria. See http://modwsgi.readthedocs.org/en/latest/release-notes/version-4.3.0.html#bugs-fixed
|
|
for more details
|
|
|
|
Once you are done, restart your Apache daemon:
|
|
|
|
.. code-block:: bash
|
|
|
|
$ sudo service apache2 restart
|
|
|
|
----
|
|
Tips
|
|
----
|
|
|
|
1. When creating a `mapping`_, note that the 'remote' attributes will be prefixed,
|
|
with `HTTP_`, so for instance, if you set OIDCClaimPrefix to `OIDC-`, then a
|
|
typical remote value to check for is: `HTTP_OIDC_ISS`.
|
|
|
|
2. Don't forget to add openid as an [auth] plugin in keystone.conf, see
|
|
`Configure authentication drivers in keystone.conf`_
|
|
|
|
.. _`Configure authentication drivers in keystone.conf`: federated_identity.html#configure-authentication-drivers-in-keystone-conf
|
|
.. _`mapping`: configure_federation.html#mapping
|