Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 3. Federation using Red Hat OpenStack Platform and Active Directory Federation Services
Red Hat supports using Microsoft Active Directory Federation Services (AD FS) as an identity provider for Red Hat OpenStack Platform (RHOSP) so that you can use the same federated solution for single sign-on in RHOSP, that exists in your wider organization.
3.1. Deploying Red Hat OpenStack Platform with Active Directory Federation Services
Use the enable-federation-openidc.yaml environment file to deploy Red Hat OpenStack Platform (RHOSP) so that it can be integrated into your federated authentication solution.
Prerequisites
- You have installed Red Hat OpenStack Platform director.
- You have Active Directory(c) for federation configured in your environment.
Procedure
Note your keystone endpoint. The keystone endpoint is the FQDN value you assign the
CloudNameparameter in thecustom-domain.yamlheat template, with the transport and port number included. The keystone endpoint has the following construction:https://<FQDN>:13000
NoteIf you do not deploy TLS, your keystone endpoint is
http://<FQDN>:5000. Red Hat recommends deploying TLS with every production deployment of RHOSP.Provide your SSO administrator with the following redirect URIs:
Redirect URIs:
https://<FQDN>:13000/v3/auth/OS-FEDERATION/identity_providers/adfsIDP/protocols/openid/websso https://<FQDN>:13000/v3/auth/OS-FEDERATION/websso/openid
-
In response, your SSO administrator provides you with a
ClientIDand aClientSecret. Copy the
enable-federation-openidc.yamlyaml file into the stack home directory:cp /usr/share/openstack-tripleo-heat-templates/environments/enable-federation-openidc.yaml \ /home/stack/
Edit your copy of the
enable-federation-openidc.yamlenvironment file. Below is a sample configuration:parameter_defaults: KeystoneAuthMethods: password,token,oauth1,mapped,application_credential,openid 1 KeystoneOpenIdcClientId: <ClientID> 2 KeystoneOpenIdcClientSecret: <ClientSecret> 3 KeystoneOpenIdcCryptoPassphrase: openstack 4 KeystoneOpenIdcIdpName: adfsIdP 5 KeystoneOpenIdcIntrospectionEndpoint: https://adfs.local.com/adfs/openid-connect/token/introspect 6 KeystoneOpenIdcProviderMetadataUrl: https://adfs.local.com/adfs/.well-known/openid-configuration 7 KeystoneOpenIdcRemoteIdAttribute: HTTP_OIDC_ISS 8 KeystoneOpenIdcResponseType: code 9 KeystoneTrustedDashboards: https://overcloud.redhat.local/dashboard/auth/websso/ 10 WebSSOChoices: [['OIDC', 'OpenID Connect']] 11 WebSSOIDPMapping: {'OIDC': ['adfsIdP', 'openid']} 12 WebSSOInitialChoice: OIDC KeystoneFederationEnable: True KeystoneOpenIdcEnable: True KeystoneOpenIdcEnableOAuth: True WebSSOEnable: True
- 1
- A comma delimited list of acceptable methods for authentication.
- 2
- Your client ID to use for the OpenID Connect provider handshake. You must get this from your SSO administrator
- 3
- The client secret to use for the OpenID Connect provider handshake. You must get this from your SSO administrator after providing your redirect URLs.
- 4
- Choose a passphrase to use when encrypting data for OpenID Connect handshake.
- 5
- The name associated with the IdP in the Identity service (keystone). The value for this parameter is always adfsIDP for Active Directory Federation Services.
- 6
- The Identity service introspection endpoint: https://{FQDN}/realms/<realm>/protocol/openid-connect/token/introspect
- 7
- The URL that points to your OpenID Connect provider metadata
- 8
- Attribute to be used to obtain the entity ID of the Identity Provider from the environment.
- 9
- Response type to be expected from the OpenID Connect provider.
- 10
- A dashboard URL trusted for single sign-on, this can also be a comma delimited list.
- 11
- Specifies the list of SSO authentication choices to present. Each item is a list of an SSO choice identifier and a display message.
- 12
- Specifies a mapping from SSO authentication choice to identity provider and protocol. The identity provider and protocol names must match the resources defined in keystone.
Add the
enable-federation-openidc.yamlto the stack with your other environment files and deploy the overcloud:(undercloud)$ openstack overcloud deploy --templates \ -e [your environment files] \ -e /home/stack/templates/enable-federation-openidc.yaml.yaml
3.2. Integrating Red Hat OpenStack Platform with Active Directory Federation Services
After you deploy Red Hat OpenStack Platform (RHOSP) with an Active Directory Federation Services (ADFS), you must complete the following steps to integrate the Identity provider (IdP) with the service provider (RHOSP).
Procedure
Create a federated domain:
openstack domain create <federated_domain_name>
Example output:
+-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | description | | | enabled | True | | id | b493634c9dbf4546a2d1988af181d7c9 | | name | my_domain | | options | {} | | tags | [] | +-------------+----------------------------------+Set up the federation identity provider.
openstack identity provider create --remote-id https://<adfs_fqdn>:9443/adfs --domain <domain_name> adfsIdP
Replace
<adfs_fqdn>with the fully qualified domain name Active Directory Federation Services Replace<federated_domain_name>with the name of the federated domain that you created in step 1.Example output:
+-------------------+-----------------------------------------------------+ | Field | Value | +-------------------+-----------------------------------------------------+ | authorization_ttl | None | | description | None | | domain_id | b493634c9dbf4546a2d1988af181d7c9 | | enabled | True | | id | adfsIdP | | remote_ids | https:/adfs.fqdn.local/adfs/ | +-------------------+-----------------------------------------------------+
Creating a mapping file. The mapping file will be unique to the identity needs of your cloud.
Example:
cat > mapping.json << EOF
[
{
"local": [
{
"user": {
"name": "{0}"
},
"group": {
"domain": {
"name": "<federated_domain>" 1
},
"name": "<federated_group_name>" 2
}
}
],
"remote": [
{
"type": "OIDC-upn" 3
}
]
}
]
EOF- 1
- The
federated_domainis the domain you created in a previous step. - 2
- Choose a name for the
federated_group_name. You will create this in a later step. - 3
- You must use `OIDC-upn`as the claim id for ADFS.
Use the mapping file to create the federation mapping rules for OpenStack. In the provided example, mapping rules created from the
mapping.jsonfile are calledADmap:openstack mapping create --rules <file> <name>
For example:
$ openstack mapping create --rules mapping.json ADmap
Create a federated group:
openstack group create --domain <federation_domain> <federation_group_name>
Create an Identity service (keystone) project:
openstack project create --domain <federation_domain> <federation_project_name>
- Add the Identity service federation group to a role.
openstack role add --group <federation_group_name> --group-domain <federation_domain> --project <federation_project_name> --project-domain <federation_domain> member
Create the OpenID federation protocol:
openstack federation protocol create openid --mapping ADmap --identity-provider adfsIdP
