Este contenido no está disponible en el idioma seleccionado.
Federate with Identity Service
Federate with Identity Service using Red Hat Single Sign-On
Abstract
Chapter 1. Overview Copiar enlaceEnlace copiado en el portapapeles!
This guide describes how to setup federation in a high availability Red Hat OpenStack Platform director environment, using a Red Hat Single Sign-On (RH-SSO) server for authentication services.
1.1. Operational Goals Copiar enlaceEnlace copiado en el portapapeles!
By following this guide, your OpenStack deployment’s authentication service will be federated with RH-SSO, and will include the following characteristics:
- Federation will be based on Security Assertion Markup Language (SAML).
- The Identity Provider (IdP) is RH-SSO, and will be situated externally to the Red Hat OpenStack Platform deployment.
- The RH-SSO IdP uses Red Hat Identity Management (IdM) as the federated user backing store. As a result, users and groups are managed in IdM, and RH-SSO will reference the user and group information that is stored in IdM.
-
Your IdM users will be authorized to access OpenStack when they are added to the IdM group:
openstack-users. -
OpenStack Keystone will have a group named
federated_users. Members of thefederated_usersgroup will have theMemberrole, which grants them permission to access the project. -
During the federated authentication process, members of the IdM group
openstack-usersare mapped into the OpenStack groupfederated_users. As a result, an IdM user will need to be a member of theopenstack-usersgroup in order to access OpenStack; if the user is not a member of the IdM groupopenstack-users, then authentication will fail.
1.2. Assumptions Copiar enlaceEnlace copiado en el portapapeles!
This guide makes the following assumptions about your deployment:
- A RH-SSO server is present, and you either have administrative privileges on the server, or the RH-SSO administrator has created a realm for you and given you administrative privileges on that realm. Since federated IdPs are external by definition, the RH-SSO server is assumed to be external to the Red Hat OpenStack Platform director overcloud.
- An IdM server is present, and also external to the Red Hat OpenStack Platform director overcloud where users and groups are managed. RH-SSO will use IdM as its User Federation backing store.
- The OpenStack deployment is based on Red Hat OpenStack Platform director.
- The Red Hat OpenStack Platform director overcloud installation uses high availability (HA) features.
- Only the Red Hat OpenStack Platform director overcloud will have federation enabled; the undercloud is not federated.
- TLS encryption is used for all external communication.
- All nodes have a Fully Qualified Domain Name (FQDN).
- HAProxy terminates TLS front-end connections, and servers running behind HAProxy do not use TLS.
- Pacemaker is used to manage some of the overcloud services, including HAProxy.
- Red Hat OpenStack Platform director has an overcloud deployed.
- You are able to SSH into the undercloud and overcloud nodes.
- The examples described in the Keystone Federation Configuration Guide will be followed.
-
On the
undercloud-0node, you will install the helper files into the home directory of thestackuser, and work in thestackuser home directory. -
On the
controller-0node, you will install the helper files into the home directory of theheat-adminuser, and work in theheat-adminuser home directory.
1.3. Prerequisites Copiar enlaceEnlace copiado en el portapapeles!
- The RH-SSO server has been configured and is external to the Red Hat OpenStack Platform director overcloud.
- The IdM deployment is external to the Red Hat OpenStack Platform director overcloud.
- Red Hat OpenStack Platform director has an overcloud deployed.
If mod_auth_mellon was previously installed on your controller nodes (perhaps because it was included in a base image used to instantiate the controller nodes) you might need to reinstall it again. This is a consequence of the way in which Puppet manages Apache modules, where the Puppet Apache class will remove any Apache configuration files not under Puppet’s control. Note that Apache will not start if these files have been removed, and it will raise errors about unknown Mellon files. At the time of this writing, mod_auth_mellon remains outside of Puppet’s control. See Section 4.14, “Prevent Puppet From Deleting Unmanaged HTTPD Files” for information on how to prevent Puppet from removing Apache configuration files.
To check if Puppet removed any of the files belonging to the mod_auth_mellon RPM, you can perform a query to validate the`mod_auth_mellon` packages, for example:
rpm -qV mod_auth_mellon
$ rpm -qV mod_auth_mellon
missing c /var/lib/config-data/puppet-generated/keystone/etc/httpd/conf.d/auth_mellon.conf
missing c /var/lib/config-data/puppet-generated/keystone/etc/httpd/conf.modules.d/10-auth_mellon.conf
If RPM indicates these configuration files are absent, then Puppet has removed then. You can then restore the files:
sudo dnf reinstall mod_auth_mellon
$ sudo dnf reinstall mod_auth_mellon
For more information, see BZ#1434875 and BZ#1497718
1.4. Accessing the OpenStack Nodes Copiar enlaceEnlace copiado en el portapapeles!
As the root user, SSH into the node hosting the OpenStack deployment. For example:
ssh root@xxx
$ ssh root@xxxCopy to Clipboard Copied! Toggle word wrap Toggle overflow SSH into the undercloud node:
ssh undercloud-0
$ ssh undercloud-0Copy to Clipboard Copied! Toggle word wrap Toggle overflow Become the
stackuser:su - stack
$ su - stackCopy to Clipboard Copied! Toggle word wrap Toggle overflow Source the overcloud configuration to enable the required OpenStack environment variables:
source overcloudrc
$ source overcloudrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteCurrently, Red Hat OpenStack Platform director sets up Keystone to use the Keystone v2 API but you will be using the Keystone v3 API. Later on in the guide you will create an
overcloudrc.v3file. From that point on you should use the v3 version of theovercloudrcfile. See Section 4.8, “Use the Keystone Version 3 API” for more information.
Afer sourcing overcloudrc, you can issue commands using the openstack command line tool, which will operate against the overcloud (even though you’re currently still logged into an undercloud node). If you need to directly access one of the overcloud nodes, you can SSH to it as the heat-admin user. For example:
ssh heat-admin@controller-0
$ ssh heat-admin@controller-0
1.5. Understanding High Availability Copiar enlaceEnlace copiado en el portapapeles!
Detailed information on high availability can be found in the High Availability Deployment and Usage guide.
-
Red Hat OpenStack Platform director distributes redundant copies of various OpenStack services across the overcloud deployment. These redundant services are deployed on the overcloud controller nodes, with director naming these nodes
controller-0,controller-1,controller-2, and so on, depending on how many controller nodes Red Hat OpenStack Platform director has configured. - The IP address of the controller nodes are private to the overcloud and are not externally visible. This is because the services running on the controller nodes are HAProxy back-end servers. There is one publically visible IP address for the set of controller nodes; this is HAProxy’s front end. When a request arrives for a service on the public IP address, then HAProxy will select a back-end server to service the request.
- The overcloud is organized as a high availability cluster. Pacemaker manages the cluster, performs health checks, and can fail over to another cluster resource if the resource stops functioning. Pacemaker is also aware of how to correctly start and stop resources.
1.5.1. HAProxy Overview Copiar enlaceEnlace copiado en el portapapeles!
HAProxy serves a similar role to Pacemaker, as it also performs health checks on the back-end servers and only forwards requests to functioning back-end servers. There is a copy of HAProxy running on all controller nodes.
Although there are N copies of HAProxy running, only one is actually fielding requests at any given time; this active HAProxy instance is managed by Pacemaker. This approach helps prevent conflicts from occurring, and allows multiple copies of HAProxy to coordinate the distribution of requests across multiple back-ends. If Pacemaker detects HAProxy has failed, it reassigns the front-end IP address to a different HAProxy instance which then becomes the controlling HAProxy instance. You might think of it as high availability for high availability. The instances of HAProxy that are kept in reserve by Pacemaker are running, but they never see an incoming connection because Pacemaker has configured the networking so that connections only route to the active HAProxy instance.
1.5.2. Managing Pacemaker Services Copiar enlaceEnlace copiado en el portapapeles!
Services that are managed by Pacemaker must not be managed by systemctl on a controller node. Use the Pacemaker pcs command instead, for example: sudo pcs resource restart haproxy-clone. You can determine the resource name using the Pacemaker status command: sudo pcs status. This will print a result similar to this:
Clone Set: haproxy-clone [haproxy] Started: [ controller-1 ] Stopped: [ controller-0 ]
Clone Set: haproxy-clone [haproxy]
Started: [ controller-1 ]
Stopped: [ controller-0 ]
1.5.3. Using the Configuration Script Copiar enlaceEnlace copiado en el portapapeles!
Many of the steps in this guide require the execution of complicated commands, so to make that task easier (and to allow for repeatability) all the commands have been gathered into a master shell script called configure-federation. Each individual step can be executed by passing the name of the step to configure-federation. The list of possible commands can be seen by using the help option (-h or --help).
You can find the script here: Chapter 6, The configure-federation file
It can be useful to know exactly what the command will be after variable substitution occurs, when the configure-federation script executes:
-
-nis dry-run mode: nothing will be modified, the exact operation will instead be written to stdout. -
-vis verbose mode: the exact operation will be written to stdout just prior to executing it. This is useful for logging.
1.5.4. Site-specific Values Copiar enlaceEnlace copiado en el portapapeles!
Certain values used in this guide are site-specific; it may otherwise have been confusing to include these site-specific values directly into this guide, and may have been a source of errors for someone attempting to replicate these steps. To address this, any site-specific values referenced in this guide are in the form of a variable. The variable name starts with a dollar-sign ($) and is all-caps with a prefix of FED_. For example, the URL used to access the RH-SSO server would be: $FED_RHSSO_URL
You can find the variables file here: Chapter 7, The fed_variables file
Site-specific values can always be identified by searching for $FED_ Site-specific values used by the configure-federation script are gathered into the file fed_variables. You will need to edit this file to suit your deployment.
1.6. Using a Proxy or SSL terminator Copiar enlaceEnlace copiado en el portapapeles!
When a server is behind a proxy, the environment it sees is different to what the client sees as the public identity of the server. A back-end server may have a different hostname, listen on a different port, or use a different protocol than what a client sees on the front side of the proxy. For many web apps this is not a major problem. Typically most of the problems occur when a server has to generate a self-referential URL (perhaps because it will redirect the client to a different URL on the same server). The URL the server generates must match the public address and port as seen by the client.
Authentication protocols are especially sensitive to the host, port and protocol (for example, HTTP/HTTPS) because they often need to assure a request was targeted at a specific server, on a specific port and on a secure transport. Proxies can interfere with this vital information, because by definition a proxy transforms a request received on its public front-end before dispatching it to a non-public server in the back-end. Similarly, responses from the non-public back-end server sometimes need adjustment so that it appears as if the response came from the public front-end of the proxy.
There are various approaches to solving this problem. Because SAML is sensitive to host, port, and protocol information, and because you are configuring SAML behind a high availability proxy (HAProxy), you must deal with these issues or your configuration will likely fail (often in cryptic ways).
1.6.1. Hostname and Port Considerations Copiar enlaceEnlace copiado en el portapapeles!
The host and port details are used in multiple contexts:
- The host and port in the URL used by the client.
- The host HTTP header inserted into the HTTP request (as derived from the client URL host).
- The host name of the front-facing proxy the client connects to. This is actually the FQDN of the IP address that the proxy is listening on.
- The host and port of the back-end server which actually handled the client request.
- The virtual host and port of the server that actually handled the client request.
It is important to understand how each of these values are used, otherwise there is a risk that the wrong host and port are used, with the result that the authentication protocols may fail because they cannot validate the parties involved in the transaction.
You can begin by considering the back-end server handling the request, because this is where the host and port are evaluated, and where most of the problems can occur:
The back-end server needs to know:
- The URL of the request (including host and port).
- Its own host and port.
Apache supports virtual name hosting, which allows a single server to host multiple domains. For example, a server running on example.com might service requests for both example.com and example-2.com, with these being virtual host names. Virtual hosts in Apache are configured inside a server configuration block, for example:
<VirtualHost> ServerName example.com </VirtualHost>
<VirtualHost>
ServerName example.com
</VirtualHost>
When Apache receives a request, it gathers the host information from the HOST HTTP header, and then tries to match the host to the ServerName in its collection of virtual hosts.
The ServerName directive defines the request scheme, hostname, and port that the server uses to identify itself. The behavior of the ServerName directive is modified by the UseCanonicalName directive. When UseCanonicalName is enabled, Apache will use the hostname and port specified in the ServerName directive to construct the canonical name for the server. This name is used in all self-referential URLs, and for the values of SERVER_NAME and SERVER_PORT in CGIs. If UseCanonicalName is Off, Apache will form self-referential URLs using the hostname and port supplied by the client, if any are supplied.
If no port is specified in the ServerName, then the server will use the port from the incoming request. For optimal reliability and predictability, you should specify an explicit hostname and port using the ServerName directive. If no ServerName is specified, the server attempts to deduce the host by first asking the operating system for the system host name, and if that fails, performing a reverse lookup for an IP address present on the system. Consequently, this will produce the wrong host information when the server is behind a proxy, therefore the use of the ServerName directive is essential.
The Apache ServerName documentation is clear concerning the need to fully specify the scheme, host, and port in the Server name directive when the server is behind a proxy, where it states:
Sometimes, the server runs behind a device that processes SSL, such as a reverse proxy, load balancer or SSL offload appliance. When this is the case, specify the https:// scheme and the port number to which the clients connect in the ServerName directive to make sure that the server generates the correct self-referential URLs.
When proxies are in effect, they use X-Forwarded-* HTTP headers to allow the entity processing the request to recognize that the request was forwarded, and what the original values were before they were forwarded. The Red Hat OpenStack Platform director HAProxy configuration sets the X-Forwarded-Proto HTTP header based on whether the front connection used SSL/TLS or not, using this configuration:
http-request set-header X-Forwarded-Proto https if { ssl_fc }
http-request set-header X-Forwarded-Proto http if !{ ssl_fc }
http-request set-header X-Forwarded-Proto https if { ssl_fc }
http-request set-header X-Forwarded-Proto http if !{ ssl_fc }
In addition, Apache does not interpret this header, so responsibility falls to another component to process it properly. In the situation where HAProxy terminates SSL prior to the back-end server processing the request, it is irrelevant that the X-Forwarded-Proto HTTP header is set to HTTPS, because Apache does not use the header when an extension module (such as mellon) asks for the protocol scheme of the request. This is why it is essential to have the ServerName directive include the scheme:://host:port and that UseCanonicalName is enabled, otherwise Apache extension modules such as mod_auth_mellon will not function properly behind a proxy.
With regard to web apps hosted by Apache behind a proxy, it is the web app’s (or rather the web app framework) responsibility to process the forwarded header. Consequently, apps handle the protocol scheme of a forwarded request differently than Apache extension modules will. Since Dashboard (horizon) is a Django web app, it is Django’s responsibility to process the X-Forwarded-Proto header. This issue arises with the origin query parameter used by horizon during authentication. Horizon adds a origin query parameter to the keystone URL it invokes to perform authentication. The origin parameter is used by horizon to redirect back to original resource.
The origin parameter generated by horizon may incorrectly specify HTTP as the scheme instead of https despite the fact horizon is running with HTTPS enabled. This occurs because Horizon calls the function build_absolute_uri() to form the origin parameter. It is entirely up to the Django to identify the scheme because build_absolute_url() is ultimately implemented by Django. You can force Django to process the X-Forwarded-Proto using a special configuration directive. This is covered in the Django secure-proxy-ssl-header documentation.
You can enable this setting by uncommenting this line in /var/lib/config-data/puppet-generated/horizon/etc/openstack-dashboard/local_settings:
#SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
#SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
Note that Django prefixes the header with "HTTP_", and converts hyphens to underscores.
After uncommenting, the Origin parameter will correctly use the HTTPS scheme. However, even when the ServerName directive includes the HTTPS scheme, the Django call build_absolute_url() will not use the HTTPS scheme. So for Django you must use the SECURE_PROXY_SSL_HEADER override, simply specifying the scheme in ServerName directive will not work. It is important to note that the Apache extension modules and web apps process the request scheme of a forwarded request differently, requiring that both the ServerName and X-Forwarded-Proto HTTP header techniques be used.
Chapter 2. Configure Red Hat Identity Management Copiar enlaceEnlace copiado en el portapapeles!
In this example, IdM is situated externally to the OpenStack Red Hat OpenStack Platform director deployment and is the source of all user and group information. RH-SSO will be configured to use IdM as its User Federation, and will then perform LDAP searches against IdM to obtain user and group information.
2.1. Create the IdM Service Account for RH-SSO Copiar enlaceEnlace copiado en el portapapeles!
Although IdM allows anonymous binds, some information is withheld for security reasons. Some of this information withheld during anonymous binds is essential for RH-SSO user federation; consequently, RH-SSO will need to bind to the IdM LDAP server with enough privileges to successfully query the required information. As a result, you will need to create a dedicated service account for RH-SSO in IdM. IdM does not natively provide a command to do this, but you can use the ldapmodify command. For example:
You can use the configure-federation script to perform the above step:
./configure-federation create-ipa-service-account
$ ./configure-federation create-ipa-service-account
2.2. Create a test user Copiar enlaceEnlace copiado en el portapapeles!
You will also need a test user account in IdM. You can either use an existing user or create a new one; the examples in this guide use "John Doe" with a uid of jdoe. You can create the jdoe user in IdM:
ipa user-add --first John --last Doe --email jdoe@example.com jdoe
$ ipa user-add --first John --last Doe --email jdoe@example.com jdoe
Assign a password to the user:
ipa passwd jdoe
$ ipa passwd jdoe
2.3. Create an IdM group for OpenStack Users Copiar enlaceEnlace copiado en el portapapeles!
Create the openstack-users group in IdM.
Make sure the
openstack-usersgroup does not already exist:ipa group-show openstack-users
$ ipa group-show openstack-users ipa: ERROR: openstack-users: group not foundCopy to Clipboard Copied! Toggle word wrap Toggle overflow Add the
openstack-usersgroup to IdM:ipa group-add openstack-users
$ ipa group-add openstack-usersCopy to Clipboard Copied! Toggle word wrap Toggle overflow Add the test user to the
openstack-usersgroup:ipa group-add-member --users jdoe openstack-users
$ ipa group-add-member --users jdoe openstack-usersCopy to Clipboard Copied! Toggle word wrap Toggle overflow Verify that the
openstack-usersgroup exists and has the test user as a member:ipa group-show openstack-users
$ ipa group-show openstack-users Group name: openstack-users GID: 331400001 Member users: jdoeCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 3. Configure RH-SSO Copiar enlaceEnlace copiado en el portapapeles!
The RH-SSO installation process is outside the scope of this guide. It is assumed you have already installed RH-SSO on a node that is situated independently from the Red Hat OpenStack Platform director deployment.
-
The RH-SSO URL will be identified by the
$FED_RHSSO_URLvariable. -
RH-SSO supports multi-tenancy, and uses realms to allow for separation between tenants. As a result, RH-SSO operations always occur within the context of a realm. This guide uses the site-specific variable
$FED_RHSSO_REALMto identify the RH-SSO realm being used. -
The RH-SSO realm can either be created ahead of time (as would be typical when RH-SSO is administered by an IT group), or the
keycloak-httpd-client-installtool can create it for you if you have administrator privileges on the RH-SSO server.
3.1. Configure the RH-SSO Realm Copiar enlaceEnlace copiado en el portapapeles!
Once the RH-SSO realm is available, use the RH-SSO web console to configure that realm for user federation against IdM:
-
Select
$FED_RHSSO_REALMfrom the drop-down list in the upper left corner. -
Select
User Federationfrom the left sideConfigurepanel. -
From the
Add provider ...drop down list in the upper right corner of theUser Federationpanel, selectldap. Fill in the following fields with these values, be sure to substitute any
$FED_site-specific variable:Expand Property Value Console Display Name
Red Hat IDM
Edit Mode
READ_ONLY
Sync Registrations
Off
Vendor
Red Hat Directory Server
Username LDAP attribute
uid
RDN LDAP attribute
uid
UUID LDAP attribute
ipaUniqueID
User Object Classes
inetOrgPerson, organizationalPerson
Connection URL
LDAPS://$FED_IPA_HOST
Users DN
cn=users,cn=accounts,$FED_IPA_BASE_DN
Authentication Type
simple
Bind DN
uid=rhsso,cn=sysaccounts,cn=etc,$FED_IPA_BASE_DN
Bind Credential
$FED_IPA_RHSSO_SERVICE_PASSWD
-
Use the
Test connectionandTest authenticationbuttons to check that user federation is working. -
Click
Saveat the bottom of theUser Federationpanel to save the new user federation provider. -
Click on the
Mapperstab at the top of the Red Hat IDM user federation page you just created. - Create a mapper to retrieve the user’s group information; this means that a user’s group memberships will be returned in the SAML assertion. You will be using group membership later to provide authorization in OpenStack.
-
Click on the
Createbutton in the upper right hand corner of the Mappers page. On the
Add user federation mapperpage, selectgroup-ldap-mapperfrom the Mapper Type drop down list, and give it the nameGroup Mapper. Fill in the following fields with these values, and be sure to substitute any$FED_site-specific variable.Expand Property Value LDAP Groups DN
cn=groups,cn=accounts„$FED_IPA_BASE_DN
Group Name LDAP Attribute
cn
Group Object Classes
groupOfNames
Membership LDAP Attribute
member
Membership Attribute Type
DN
Mode
READ_ONLY
User Groups Retrieve Strategy
GET_GROUPS_FROM_USER_MEMBEROF_ATTRIBUTE
-
Click
Save.
3.2. Add User Attributes for SAML Assertion Copiar enlaceEnlace copiado en el portapapeles!
The SAML assertion can send to keystone the properties that are bound to the user (for example, user metadata); these are called attributes in SAML. You will need to configure RH-SSO to return the required attributes in the assertion. Then, when keystone receives the SAML assertion, it will map those attributes into user metadata in a manner which keystone can then process. The process of mapping IdP attributes into keystone data is called Federated Mapping and will be covered later in this guide (see Section 4.21, “Create the Mapping File and Upload to Keystone”).
RH-SSO calls the process of adding returned attributes Protocol Mapping. Protocol mapping is a property of the RH-SSO client (for example, the service provider (SP) added to the RH-SSO realm). The process for adding a given attribute to SAML follows a similar process.
In the RH-SSO administration web console:
-
Select
$FED_RHSSO_REALMfrom the drop-down list in the upper left corner. -
Select
Clientsfrom the left sideConfigurepanel. -
Select the SP client that was setup by
keycloak-httpd-client-install. It will be identified by its SAMLEntityId. -
Select the
Mapperstab from the horizontal list of tabs appearing at the top of the client panel. -
In the
Mapperspanel in the upper right are two buttons:CreateandAdd Builtin. Use one of these buttons to add a protocol mapper to the client.
You can add any required attributes, but for this exercise you will only need the list of groups the user is a member of (because group membership is how you will authorize the user).
3.3. Add Group Information to the Assertion Copiar enlaceEnlace copiado en el portapapeles!
-
Click on the
Createbutton in theMapperspanel. -
In the
Create Protocol Mapperpanel selectGroup listfrom theMapper typedrop-down list. -
Enter
Group Listas a name in theNamefield. Enter
groupsas the name of the SAML attribute in theGroup attribute namefield.NoteThis is the name of the attribute as it will appear in the SAML assertion. When the keystone mapper searches for names in the
Remotesection of the mapping declaration, it is the SAML attribute names it is looking for. Whenever you add an attribute in RH-SSO to be passed in the assertion you will need to specify the SAML attribute name; it is the RH-SSO protocol mapper where that name is defined.-
In the
SAML Attribute NameFormatfield selectBasic. -
In the
Single Group Attributetoggle box selectOn. -
Click
Saveat the bottom of the panel.
keycloak-httpd-client-install adds a group mapper when it runs.
Chapter 4. Configure OpenStack for Federation Copiar enlaceEnlace copiado en el portapapeles!
4.1. Determine the IP Address and FQDN Settings Copiar enlaceEnlace copiado en el portapapeles!
The following nodes require an assigned Fully-Qualified Domain Name (FQDN):
- The host running the Dashboard (horizon).
-
The host running the Identity Service (keystone), referenced in this guide as
$FED_KEYSTONE_HOST. Note that more than one host will run a service in a high-availability environment, so the IP address is not a host address but rather the IP address bound to the service. - The host running RH-SSO.
- The host running IdM.
The Red Hat OpenStack Platform director deployment does not configure DNS or assign FQDNs to the nodes, however, the authentication protocols (and TLS) require the use of FQDNs. As a result, you must determine the external public IP address of the overcloud. Note that you need the IP address of the overcloud, which is not the same as the IP address allocated to an individual node in the overcloud, such as controller-0, controller-1.
You will need the external public IP address of the overcloud because IP addresses are assigned to a high availability cluster, instead of an individual node. Pacemaker and HAProxy work together to provide the appearance of a single IP address; this IP address is entirely distinct from the individual IP address of any given node in the cluster. As a result, the correct way to think about the IP address of an OpenStack service is not in terms of which node that service is running on, but rather to consider the effective IP address that the cluster is advertising for that service (for example, the VIP).
4.1.1. Retrieve the IP address Copiar enlaceEnlace copiado en el portapapeles!
In order to determine the correct IP address, you will need to assign a name to it, instead of using DNS. There are two ways to do this:
Red Hat OpenStack Platform director uses one common public IP address for all OpenStack services, and separates those services on the single public IP address by port number; if you the know public IP address of one service in the OpenStack cluster then you know all of them (however that does not also tell you the port number of a service). You can examine the Keystone URL in the
overcloudrcfile located in the~stackhome directory on the undercloud. For example:export OS_AUTH_URL=https://10.0.0.101:13000/v2.0
export OS_AUTH_URL=https://10.0.0.101:13000/v2.0Copy to Clipboard Copied! Toggle word wrap Toggle overflow This tells you that the public keystone IP address is
10.0.0.101and that keystone is available on port13000. By extension, all other OpenStack services are also available on the10.0.0.101IP address with their own unique port number.However, the more accurate way of determining the IP addresses and port number information is to examine the HAProxy configuration file (
/var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg), which is located on each of the overcloud nodes. Thehaproxy.cfgfile is an identical copy on each of the overcloud controller nodes; this is essential because Pacemaker will assign one controller node the responsibility of running HAProxy for the cluster, in the event of an HAProxy failure Pacemaker will reassign a different overcloud controller to run HAProxy. No matter which controller node is currently running HAProxy, it must act identically; therefore thehaproxy.cfgfiles must be identical.-
To examine the
haproxy.cfgfile, SSH into one of the cluster’s controller nodes and review/var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg. As noted above it does not matter which controller node you select. -
The
haproxy.cfgfile is divided into sections, with each beginning with alistenstatement followed by the name of the service. Immediately inside the service section is abindstatement; these are the front IP addresses, some of which are public, and others are internal to the cluster. Theserverlines are the back IP addresses where the service is actually running, there should be oneserverline for each controller node in the cluster. To determine the public IP address and port of the service from the multiple
bindentries in the section:Red Hat OpenStack Platform director puts the public IP address as the first
bindentry. In addition, the public IP address should support TLS, so thebindentry will have thesslkeyword. The IP address should also match the IP address set in theOS_AUTH_URLlocated in theoverstackrcfile. For example, here is a samplekeystone_publicsection from ahaproxy.cfg:Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
The first
bindline has thesslkeyword, and the IP address matches that of theOS_AUTH_URLlocated in theoverstackrcfile. As a result, you can be confident that keystone is publicly accessed at the IP address of10.0.0.101on port13000. -
The second
bindline is internal to the cluster, and is used by other OpenStack services running in the cluster (note that it does not use TLS because it is not public). -
The
mode httpsetting indicates that the protocol in use isHTTP, this allows HAProxy to examine HTTP headers, among other tasks. The
X-Forwarded-Protolines:http-request set-header X-Forwarded-Proto https if { ssl_fc } http-request set-header X-Forwarded-Proto http if !{ ssl_fc }http-request set-header X-Forwarded-Proto https if { ssl_fc } http-request set-header X-Forwarded-Proto http if !{ ssl_fc }Copy to Clipboard Copied! Toggle word wrap Toggle overflow These settings require particular attention and will be covered in more detail in Section 4.1.2, “Set the Host Variables and Name the Host”. They guarantee that the HTTP header
X-Forwarded-Protowill be set and seen by the back-end server. The back-end server in many cases needs to know if the client was usingHTTPS. However, HAProxy terminates TLS so the back-end server will see the connection as non-TLS. TheX-Forwarded-ProtoHTTP header is a mechanism that allows the back-end server identify which protocol the client was actually using, instead of which protocol the request arrived on. It is essential that a client can not be able to send aX-Forwarded-ProtoHTTP header, because that would allow the client to maliciously spoof that the protocol wasHTTPS. TheX-Forwarded-ProtoHTTP header can either be deleted by the proxy when it is received from the client, or the proxy can forcefully set it and so mitigate any malicious use by the client. This is whyX-Forwarded-Protowill always be set to one ofhttpsorhttp.The X-Forwarded-For HTTP header is used to track the client, which allows the back-end server to identify who the requesting client was instead of it appearing to be the proxy. This option causes the
X-Forwarded-For HTTPheader to be inserted into the request:option forwardfor
option forwardforCopy to Clipboard Copied! Toggle word wrap Toggle overflow See Section 4.1.2, “Set the Host Variables and Name the Host” for more information on forwarded proto, redirects, ServerName, among others.
The following line will confirm that only HTTPS is used on the public IP address:
redirect scheme https code 301 if { hdr(host) -i 10.0.0.101 } !{ ssl_fc }redirect scheme https code 301 if { hdr(host) -i 10.0.0.101 } !{ ssl_fc }Copy to Clipboard Copied! Toggle word wrap Toggle overflow This setting identifies if the request was received on the public IP address (for example
10.0.0.101) and it was not HTTPS, then performs a301 redirectand sets the scheme to HTTPS.HTTP servers (such as Apache) often generate self-referential URLs for redirect purposes. This redirect location must indicate the correct protocol, but if the server is behind a TLS terminator it will think its redirection URL should be HTTP and not HTTPS. This line identifies if a Location header appears in the response that uses the HTTP scheme, then rewrites it to use the HTTPS scheme:
rsprep ^Location:\ http://(.*) Location:\ https://\1
rsprep ^Location:\ http://(.*) Location:\ https://\1Copy to Clipboard Copied! Toggle word wrap Toggle overflow
-
To examine the
4.1.2. Set the Host Variables and Name the Host Copiar enlaceEnlace copiado en el portapapeles!
You will need to determine the IP address and port to use. In this example the IP address is 10.0.0.101 and the port is 13000.
This value can be confirmed in
overcloudrc:export OS_AUTH_URL=https://10.0.0.101:13000/v2.0
export OS_AUTH_URL=https://10.0.0.101:13000/v2.0Copy to Clipboard Copied! Toggle word wrap Toggle overflow And in the
keystone_publicsection of thehaproxy.cfgfile:bind 10.0.0.101:13000 transparent ssl crt /etc/pki/tls/private/overcloud_endpoint.pem
bind 10.0.0.101:13000 transparent ssl crt /etc/pki/tls/private/overcloud_endpoint.pemCopy to Clipboard Copied! Toggle word wrap Toggle overflow You must also give the IP address a FQDN. This example uses
overcloud.localdomain. Note that the IP address should be put in the/etc/hostsfile since DNS is not being used:10.0.0.101 overcloud.localdomain # FQDN of the external VIP
10.0.0.101 overcloud.localdomain # FQDN of the external VIPCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteRed Hat OpenStack Platform director is expected to have already configured the hosts files on the overcloud nodes, but you may need to add the host entry on any external hosts that participate.
The
$FED_KEYSTONE_HOSTand$FED_KEYSTONE_HTTPS_PORTmust be set in thefed_variablesfile. Using the above example values:FED_KEYSTONE_HOST="overcloud.localdomain" FED_KEYSTONE_HTTPS_PORT=13000
FED_KEYSTONE_HOST="overcloud.localdomain" FED_KEYSTONE_HTTPS_PORT=13000Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Because Mellon is running on the Apache server that hosts keystone, the Mellon host:port and keystone host:port values will match.
If you run hostname on one of the controller nodes it will likely be similar to this: controller-0.localdomain, but note that this is its internal cluster name, not its public name. You will instead need to use the public IP address.
4.2. Install Helper Files on undercloud-0 Copiar enlaceEnlace copiado en el portapapeles!
-
Copy the
configure-federationandfed_variablesfiles into the~stackhome directory onundercloud-0. You will have created these files as part of Section 1.5.3, “Using the Configuration Script”.
4.3. Set your Deployment Variables Copiar enlaceEnlace copiado en el portapapeles!
-
The file
fed_variablescontains variables specific to your federation deployment. These variables are referenced in this guide as well as in theconfigure-federationhelper script. Each site-specific federation variable is prefixed withFED_and (when used as a variable) will use the$variable syntax, such as$FED_. Make sure everyFED_variable infed_variablesis provided a value.
4.4. Copy the Helper Files From undercloud-0 to controller-0 Copiar enlaceEnlace copiado en el portapapeles!
Copy the
configure-federationand the editedfed_variablesfrom the~stackhome directory on undercloud-0 to the~heat-adminhome directory oncontroller-0. For example:scp configure-federation fed_variables heat-admin@controller-0:/home/heat-admin
$ scp configure-federation fed_variables heat-admin@controller-0:/home/heat-adminCopy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the configure-federation script to perform the above step: $ ./configure-federation copy-helper-to-controller
4.5. Initialize the Working Environment on the undercloud Copiar enlaceEnlace copiado en el portapapeles!
On the undercloud node, as the stack user, create the
fed_deploymentdirectory. This location will be the file stash. For example:su - stack mkdir fed_deployment
$ su - stack $ mkdir fed_deploymentCopy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the configure-federation script to perform the above step: $ ./configure-federation initialize
4.6. Initialize the Working Environment on controller-0 Copiar enlaceEnlace copiado en el portapapeles!
From the undercloud node, SSH into the
controller-0node as theheat-adminuser and create thefed_deploymentdirectory. This location will be the file stash. For example:ssh heat-admin@controller-0 mkdir fed_deployment
$ ssh heat-admin@controller-0 $ mkdir fed_deploymentCopy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the configure-federation script to perform the above step. From the controller-0 node: $ ./configure-federation initialize
4.7. Install mod_auth_mellon on Each Controller Node Copiar enlaceEnlace copiado en el portapapeles!
From the undercloud node, SSH into the controller-n node as the
heat-adminuser and install themod_auth_mellon. For example:ssh heat-admin@controller-n # replace n with controller number sudo dnf reinstall mod_auth_mellon
$ ssh heat-admin@controller-n # replace n with controller number $ sudo dnf reinstall mod_auth_mellonCopy to Clipboard Copied! Toggle word wrap Toggle overflow
If mod_auth_mellon is already installed on the controller nodes, you may need to reinstall it again. See the Reinstall mod_auth_mellon note for more details.
You can use the configure-federation script to perform the above step: $ ./configure-federation install-mod-auth-mellon
4.8. Use the Keystone Version 3 API Copiar enlaceEnlace copiado en el portapapeles!
Before you can use the openstack command line client to administer the overcloud, you will need to configure certain parameters. Normally this is done by sourcing an rc file within your shell session, which sets the required environment variables. Red Hat OpenStack Platform director will have created an overcloudrc file for this purpose in the home directory of the stack user, in the undercloud-0 node. By default, the overcloudrc file is set to use the v2 version of the keystone API, however, federation requires the use of the v3 keystone API. As a result, you need to create a new rc file that uses the v3 keystone API.
For example:
source overcloudrc NEW_OS_AUTH_URL=`echo $OS_AUTH_URL | sed 's!v2.0!v3!'`
$ source overcloudrc $ NEW_OS_AUTH_URL=`echo $OS_AUTH_URL | sed 's!v2.0!v3!'`Copy to Clipboard Copied! Toggle word wrap Toggle overflow Write the following contents to
overcloudrc.v3:Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteYou can use the
configure-federationscript to perform the above step:$ ./configure-federation create-v3-rcfileFrom this point forward, to work with the overcloud you will use the
overcloudrc.v3file:ssh undercloud-0 su - stack source overcloudrc.v3
$ ssh undercloud-0 $ su - stack $ source overcloudrc.v3Copy to Clipboard Copied! Toggle word wrap Toggle overflow
4.9. Add the RH-SSO FQDN to Each Controller Copiar enlaceEnlace copiado en el portapapeles!
The mellon service will be running on each controller node and configured to connect to the RH-SSO IdP.
If the FQDN of the RH-SSO IdP is not resolvable through DNS then you will have to manually add the FQDN to the
/etc/hostsfile on all controller nodes (after the Heat Hosts section):Copy to Clipboard Copied! Toggle word wrap Toggle overflow
4.10. Install and Configure Mellon on the Controller Node Copiar enlaceEnlace copiado en el portapapeles!
The keycloak-httpd-client-install tool performs many of the steps needed to configure mod_auth_mellon and have it authenticate against the RH-SSO IdP. The keycloak-httpd-client-install tool should be run on the node where mellon will run. In our case this means mellon will be running on the overcloud controllers protecting Keystone.
Note that this is a high availability deployment, and as such there will be multiple overcloud controller nodes, each running identical copies. As a result, the mellon setup will need to be replicated across each controller node. You will approach this by installing and configuring mellon on controller-0, and then gathering up all the configuration files that the keycloak-httpd-client-install tool created into an archive (for example, a tar file) and then let swift copy the archive over to each controller and unarchive the files there.
Run the RH-SSO client installation:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteYou can use
configure-federationscript to perform the above step:$ ./configure-federation client-installAfter the client RPM installation, you should see output similar to this:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
4.11. Edit the Mellon Configuration Copiar enlaceEnlace copiado en el portapapeles!
Additional mellon configuration is required for your deployment: As you will be using a list of groups during the IdP-assertion-to-Keystone mapping phase, the keystone mapping engine expects lists to be in a certain format (one value with items separated by a semicolon (;)). As a result, you must configure mellon so that when it receives multiple values for an attribute, it must know to combine the multiple attributes into a single value with items separated by a semicolon. This mellon directive will address that:
MellonMergeEnvVars On ";"
MellonMergeEnvVars On ";"
To configure this setting in your deployment:
vi /var/lib/config-data/puppet-generated/keystone/etc/httpd/conf.d/v3_mellon_keycloak_openstack.conf
$ vi /var/lib/config-data/puppet-generated/keystone/etc/httpd/conf.d/v3_mellon_keycloak_openstack.confCopy to Clipboard Copied! Toggle word wrap Toggle overflow Locate the
<Location /v3>block and add a line to it. For example:<Location /v3> ... MellonMergeEnvVars On ";" </Location><Location /v3> ... MellonMergeEnvVars On ";" </Location>Copy to Clipboard Copied! Toggle word wrap Toggle overflow
4.12. Create an Archive of the Generated Configuration Files Copiar enlaceEnlace copiado en el portapapeles!
The mellon configuration needs to be replicated across all controller nodes, so you will create an archive of the files that allows you to install the exact same file contents on each controller node. The archive will be stored in the ~heat-admin/fed_deployment subdirectory.
Create the compressed tar archive:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the configure-federation script to perform the above step: $ ./configure-federation create-sp-archive
4.13. Retrieve the Mellon Configuration Archive Copiar enlaceEnlace copiado en el portapapeles!
On the
undercloud-0node, fetch the archive you just created and extract the files, as you will need access some of the data in subsequent steps (for example theentityIDof the RH-SSO IdP).scp heat-admin@controller-0:/home/heat-admin/fed_deployment/rhsso_config.tar.gz ~/fed_deployment tar -C fed_deployment -xvf fed_deployment/rhsso_config.tar.gz
$ scp heat-admin@controller-0:/home/heat-admin/fed_deployment/rhsso_config.tar.gz ~/fed_deployment $ tar -C fed_deployment -xvf fed_deployment/rhsso_config.tar.gzCopy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the configure-federation script to perform the above step: $ ./configure-federation fetch-sp-archive
4.14. Prevent Puppet From Deleting Unmanaged HTTPD Files Copiar enlaceEnlace copiado en el portapapeles!
By default, the Puppet Apache module will purge any files in the Apache configuration directories it is not managing. This is considered a reasonable precaution, as it prevents Apache from operating in any manner other than the configuration enforced by Puppet. However, this conflicts with the manual configuration of mellon in the HTTPD configuration directories. When the Apache Puppet apache::purge_configs flag is enabled (which it is by default), Puppet will delete files belonging to the mod_auth_mellon RPM when the mod_auth_mellon RPM is installed. It will also delete the configuration files generated by keycloak-httpd-client-install when it is run. Until the mellon files are under Puppet control, you will have to disable the apache::purge_configs flag.
You may also want to check if the mod_auth_mellon configuration files have already been removed in a previous run of overcloud_deploy, see Reinstall mod_auth_mellon for more information.
Disabling the apache::purge_configs flag opens the controller nodes to vulnerabilities. Do not forget to re-enable it when Puppet adds support for managing mellon.
To override the apache::purge_configs flag, create a Puppet file containing the override and add the override file to the list of Puppet files used when overcloud_deploy.sh is run.
Create the file
fed_deployment/puppet_override_apache.yamland add this content:parameter_defaults: ControllerExtraConfig: apache::purge_configs: falseparameter_defaults: ControllerExtraConfig: apache::purge_configs: falseCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
Add the file near the end of the
overcloud_deploy.shscript. It should be the last-eargument. For example:
-e /home/stack/fed_deployment/puppet_override_apache.yaml \ --log-file overcloud_deployment_14.log &> overcloud_install.log
-e /home/stack/fed_deployment/puppet_override_apache.yaml \
--log-file overcloud_deployment_14.log &> overcloud_install.log
You can use the configure-federation script to perform the above step: $ ./configure-federation puppet-override-apache
4.15. Configure Keystone for Federation Copiar enlaceEnlace copiado en el portapapeles!
This guide uses keystone domains, which require some extra configuration. If enabled, the keystone Puppet module can perform this extra configuration step.
In one of the Puppet YAML files, add the following:
keystone::using_domain_config: true
keystone::using_domain_config: trueCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Some additional values must be set in /etc/keystone/keystone.conf to enable federation:
-
auth:methods -
federation:trusted_dashboard -
federation:sso_callback_template -
federation:remote_id_attribute
An explanation of these configuration settings and their suggested values:
-
auth:methods- A list of allowed authentication methods. By default the list is:['external', 'password', 'token', 'oauth1']. You will need to enable SAML using themappedmethod, so this value should be:external,password,token,oauth1,mapped. -
federation:trusted_dashboard- A list of trusted dashboard hosts. Before accepting a Single Sign-On request to return a token, the origin host must be a member of this list. This configuration option may be repeated for multiple values. You must set this in order to use web-based SSO flows. For this deployment the value would be:https://$FED_KEYSTONE_HOST/dashboard/auth/websso/Note that the host is $FED_KEYSTONE_HOST only because Red Hat OpenStack Platform director co-locates both keystone and horizon on the same host. If horizon is running on a different host to keystone, then you will need to adjust accordingly. -
federation:sso_callback_template- The absolute path to a HTML file used as a Single Sign-On callback handler. This page is expected to redirect the user from keystone back to a trusted dashboard host, by form encoding a token in aPOSTrequest. Keystone’s default value should be sufficient for most deployments:/etc/keystone/sso_callback_template.html federation:remote_id_attribute- The value used to obtain the entity ID of the Identity Provider. Formod_auth_mellonyou will useMELLON_IDP. Note that this is set in the mellon configuration file using theMellonIdP IDPdirective.Create the
fed_deployment/puppet_override_keystone.yamlfile with this content:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Towards the end of the
overcloud_deploy.shscript, add the file you just created. It should be the last-eargument. For example:-e /home/stack/fed_deployment/puppet_override_keystone.yaml \ --log-file overcloud_deployment_14.log &> overcloud_install.log
-e /home/stack/fed_deployment/puppet_override_keystone.yaml \ --log-file overcloud_deployment_14.log &> overcloud_install.logCopy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the configure-federation script to perform the above step: $ ./configure-federation puppet-override-keystone
4.16. Deploy the Mellon Configuration Archive Copiar enlaceEnlace copiado en el portapapeles!
You will use swift artifacts to install the mellon configuration files on each controller node. For example:
source ~/stackrc upload-swift-artifacts -f fed_deployment/rhsso_config.tar.gz
$ source ~/stackrc
$ upload-swift-artifacts -f fed_deployment/rhsso_config.tar.gz
You can use the configure-federation script to perform the above step: $ ./configure-federation deploy-mellon-configuration
4.17. Redeploy the Overcloud Copiar enlaceEnlace copiado en el portapapeles!
In earlier steps you made changes to the Puppet YAML configuration files and swift artifacts. These changes can now be applied using this command:
./overcloud_deploy.sh
$ ./overcloud_deploy.sh
In later steps, other configuration changes will be made to the overcloud controller nodes. Re-running Puppet using the overcloud_deploy.sh script may overwrite some of these changes. You should avoid applying the Puppet configuration from this point forward to avoid losing any manual edits that were made to the configuration files on the overcloud controller nodes.
4.18. Use Proxy Persistence for Keystone on Each Controller Copiar enlaceEnlace copiado en el portapapeles!
With high availability, any one of the multiple back-end servers can be expected to field a request. Because of the number of redirections used by SAML, and the fact each of those redirections involves state information, it is vital that the same server processes all the transactions. In addition, a session will be established by mod_auth_mellon. Currently mod_auth_mellon is not capable of sharing its state information across multiple servers, so you must configure HAProxy to always direct requests from a client to the same server each time.
HAProxy can bind a client to the same server using either affinity or persistence. This article on HAProxy Sticky Sessions provides valuable background material.
The difference between persistence and affinity is that affinity is used when information from a layer below the application layer is used to pin a client request to a single server. Persistence is used when the application layer information binds a client to a single server sticky session. The main advantage of persistence over affinity is that it is much more accurate.
Persistence is implemented through the use of cookies. The HAProxy cookie directive names the cookie that will be used for persistence, along with parameters controlling its use. The HAProxy server directive has a cookie option that sets the value of the cookie, which should be set to the name of the server. If an incoming request does not have a cookie identifying the back-end server, then HAProxy selects a server based on its configured balancing algorithm. HAProxy ensures that the cookie is set to the name of the selected server in the response. If the incoming request has a cookie identifying a back-end server then HAProxy automatically selects that server to handle the request.
To enable persistence in the
keystone_publicblock of the/var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfgconfiguration file, add this line:cookie SERVERID insert indirect nocache
cookie SERVERID insert indirect nocacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow This setting states that
SERVERIDwill be the name of the persistence cookie.Next, you must edit each
serverline and addcookie <server-name>as an additional option. For example:server controller-0 cookie controller-0 server controller-1 cookie controller-1
server controller-0 cookie controller-0 server controller-1 cookie controller-1Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Note that the other parts of the server directive have been omitted for clarity.
4.19. Create Federated Resources Copiar enlaceEnlace copiado en el portapapeles!
You might recall from the introduction that you are going to follow the federation example in the Create keystone groups and assign roles section of the keystone federation documentation.
Perform the following steps on the undercloud node as the
stackuser (after sourcing theovercloudrc.v3file):openstack domain create federated_domain openstack project create --domain federated_domain federated_project openstack group create federated_users --domain federated_domain openstack role add --group federated_users --group-domain federated_domain --domain federated_domain _member_ openstack role add --group federated_users --group-domain federated_domain --project federated_project _member_
$ openstack domain create federated_domain $ openstack project create --domain federated_domain federated_project $ openstack group create federated_users --domain federated_domain $ openstack role add --group federated_users --group-domain federated_domain --domain federated_domain _member_ $ openstack role add --group federated_users --group-domain federated_domain --project federated_project _member_Copy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the configure-federation script to perform the above step: $ ./configure-federation create-federated-resources
4.20. Create the Identity Provider in OpenStack Copiar enlaceEnlace copiado en el portapapeles!
The IdP needs to be registered in keystone, which creates a binding between the entityID in the SAML assertion and the name of the IdP in keystone.
You will need to locate the entityID of the RH-SSO IdP. This value is located in the IdP metadata which was obtained when keycloak-httpd-client-install was run. The IdP metadata is stored in the /var/lib/config-data/puppet-generated/keystone/etc/httpd/saml2/v3_keycloak_$FED_RHSSO_REALM_idp_metadata.xml file. In an earlier step you retrieved the mellon configuration archive and extracted it to the fed_deployment work area. As a result, you can find the IdP metadata in fed_deployment/var/lib/config-data/puppet-generated/keystone/etc/httpd/saml2/v3_keycloak_$FED_RHSSO_REALM_idp_metadata.xml. In the IdP metadata file, you will find a <EntityDescriptor> element with a entityID attribute. You need the value of the entityID attribute, and for example purposes this guide will assume it has been stored in the $FED_IDP_ENTITY_ID variable. You can name your IdP rhsso, which is assigned to the variable $FED_OPENSTACK_IDP_NAME. For example:
openstack identity provider create --remote-id $FED_IDP_ENTITY_ID $FED_OPENSTACK_IDP_NAME
$ openstack identity provider create --remote-id $FED_IDP_ENTITY_ID $FED_OPENSTACK_IDP_NAME
You can use the configure-federation script to perform the above step: $ ./configure-federation openstack-create-idp
4.21. Create the Mapping File and Upload to Keystone Copiar enlaceEnlace copiado en el portapapeles!
Keystone performs a mapping to match the IdP’s SAML assertion into a format that keystone can understand. The mapping is performed by keystone’s mapping engine and is based on a set of mapping rules that are bound to the IdP.
These are the mapping rules used in this example (as described in the introduction):
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
This mapping file contains only one rule. Rules are divided into two parts: local and remote. The mapping engine works by iterating over the list of rules until one matches, and then executing it. A rule is considered a match only if all the conditions in the remote part of the rule match. In this example the remote conditions specify:
-
The assertion must contain a value called
MELLON_NAME_ID. -
The assertion must contain a values called
MELLON_groupsand at least one of the groups in the group list must beopenstack-users.
If the rule matches, then:
-
The keystone
username will be assigned the value fromMELLON_NAME_ID. -
The user will be assigned to the keystone group
federated_usersin theDefaultdomain.
In summary, if the IdP successfully authenticates the user, and the IdP asserts that user belongs to the group openstack-users, then keystone will allow that user to access OpenStack with the privileges bound to the federated_users group in keystone.
4.21.1. Create the mapping Copiar enlaceEnlace copiado en el portapapeles!
To create the mapping in keystone, create a file containing the mapping rules and then upload it into keystone, giving it a reference name. Create the mapping file in the
fed_deploymentdirectory (for example, infed_deployment/mapping_${FED_OPENSTACK_IDP_NAME}_saml2.json), and assign the name$FED_OPENSTACK_MAPPING_NAMEto the mapping rules. For example:openstack mapping create --rules fed_deployment/mapping_rhsso_saml2.json $FED_OPENSTACK_MAPPING_NAME
$ openstack mapping create --rules fed_deployment/mapping_rhsso_saml2.json $FED_OPENSTACK_MAPPING_NAMECopy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the configure-federation script to perform the above procedure as two steps:
./configure-federation create-mapping ./configure-federation openstack-create-mapping
$ ./configure-federation create-mapping
$ ./configure-federation openstack-create-mapping
-
create-mapping- creates the mapping file. -
openstack-create-mapping- performs the upload of the file.
4.22. Create a Keystone Federation Protocol Copiar enlaceEnlace copiado en el portapapeles!
Keystone uses the
Mappedprotocol to bind an IdP to a mapping. To establish this binding:openstack federation protocol create \ --identity-provider $FED_OPENSTACK_IDP_NAME \ --mapping $FED_OPENSTACK_MAPPING_NAME \ mapped"
$ openstack federation protocol create \ --identity-provider $FED_OPENSTACK_IDP_NAME \ --mapping $FED_OPENSTACK_MAPPING_NAME \ mapped"Copy to Clipboard Copied! Toggle word wrap Toggle overflow
You can use the configure-federation script to perform the above step: $ ./configure-federation openstack-create-protocol
4.23. Fully-Qualify the Keystone Settings Copiar enlaceEnlace copiado en el portapapeles!
On each controller node, edit
/var/lib/config-data/puppet-generated/keystone/etc/httpd/conf.d/10-keystone_wsgi_main.confto confirm that theServerNamedirective inside theVirtualHostblock includes the HTTPS scheme, the public hostname, and the public port. You must also enable theUseCanonicalNamedirective. For example:<VirtualHost> ServerName https:$FED_KEYSTONE_HOST:$FED_KEYSTONE_HTTPS_PORT UseCanonicalName On ... </VirtualHost>
<VirtualHost> ServerName https:$FED_KEYSTONE_HOST:$FED_KEYSTONE_HTTPS_PORT UseCanonicalName On ... </VirtualHost>Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Be sure to substitute the $FED_ variables with the values specific to your deployment.
4.24. Configure Horizon to Use Federation Copiar enlaceEnlace copiado en el portapapeles!
On each controller node, edit
/var/lib/config-data/puppet-generated/horizon/etc/openstack-dashboard/local_settingsand make sure the following configuration values are set:Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Be sure to substitute the $FED_ variables with the values specific to your deployment.
4.25. Configure Horizon to Use the X-Forwarded-Proto HTTP Header Copiar enlaceEnlace copiado en el portapapeles!
On each controller node, edit
/var/lib/config-data/puppet-generated/horizon/etc/openstack-dashboard/local_settingsand uncomment the line:#SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')#SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')Copy to Clipboard Copied! Toggle word wrap Toggle overflow
You must restart a container for configuration changes to take effect.
Chapter 5. Troubleshooting Copiar enlaceEnlace copiado en el portapapeles!
5.1. Test the Keystone Mapping Rules Copiar enlaceEnlace copiado en el portapapeles!
It is recommended you verify that your mapping rules work as expected. The keystone-manage command line tool allows you to exercise a set of mapping rules (read from a file) against assertion data which is also read from a file. For example:
The file
mapping_rules.jsonhas this content:Copy to Clipboard Copied! Toggle word wrap Toggle overflow The file
assertion_data.txthas this content:MELLON_NAME_ID: 'G-90eb44bc-06dc-4a90-aa6e-fb2aa5d5b0de MELLON_groups: openstack-users;ipausers
MELLON_NAME_ID: 'G-90eb44bc-06dc-4a90-aa6e-fb2aa5d5b0de MELLON_groups: openstack-users;ipausersCopy to Clipboard Copied! Toggle word wrap Toggle overflow If you then run this command:
keystone-manage mapping_engine --rules mapping_rules.json --input assertion_data.txt
$ keystone-manage mapping_engine --rules mapping_rules.json --input assertion_data.txtCopy to Clipboard Copied! Toggle word wrap Toggle overflow You should get this mapped result:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
You can also include the --engine-debug command line argument, which will output diagnostic information describing how the mapping rules are being evaluated.
5.2. Determine the Actual Assertion Values Received by Keystone Copiar enlaceEnlace copiado en el portapapeles!
The mapped assertion values that keystone will use are passed as CGI environment variables. To retrieve a dump of those environment variables:
Create the following test script in
/var/www/cgi-bin/keystone/testwith the following content:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the
/var/lib/config-data/puppet-generated/keystone/etc/httpd/conf.d/10-keystone_wsgi_main.conffile setting it to run thetestscript by temporarily modifying theWSGIScriptAliasdirective:WSGIScriptAlias "/v3/auth/OS-FEDERATION/websso/mapped" "/var/www/cgi-bin/keystone/test"
WSGIScriptAlias "/v3/auth/OS-FEDERATION/websso/mapped" "/var/www/cgi-bin/keystone/test"Copy to Clipboard Copied! Toggle word wrap Toggle overflow Restart httpd:
systemctl restart httpd
systemctl restart httpdCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
Attempt to login, and review the information that the script dumps out. When finished, remember to restore the
WSGIScriptAliasdirective, and restart the HTTPD service again.
5.3. Review the SAML messages exchanged between the SP and IdP Copiar enlaceEnlace copiado en el portapapeles!
The SAMLTracer Firefox add-on is a useful tool for capturing and displaying the SAML messages exchanged between the SP and the IdP.
-
Install
SAMLTracerfrom this URL: https://addons.mozilla.org/en-US/firefox/addon/saml-tracer/ -
Enable
SAMLTracerfrom the Firefox menu. ASAMLTracerpop-up window will appear in which all browser requests are displayed. If a request is detected as a SAML message a specialSAMLicon is added to the request. - Initiate a SSO login from the Firefox browser.
-
In the
SAMLTracerwindow find the firstSAMLmessage and click on it. Use theSAMLtab in the window to see the decoded SAML message (note, the tool is not capable of decrypting encrypted content in the body of the message, if you need to see encrypted content you must disable encryption in the metadata). The first SAML message should be anAuthnRequestsent by the SP to the IdP. The second SAML message should be the assertion response sent by the IdP. Since the SAML HTTP-Redirect profile is being used the Assertion response will be wrapped in a POST. Click on theSAMLtab to see the contents of the assertion.