Adding identity providers

Before connecting to an identity provider and importing its users, you need to create domain groups for these users and assign respective roles to these groups.

Prerequisites

Local domain groups are created, as described in Creating domain groups.
The redirection URL (redirect_uri) for the cluster must be https://<url>:5000/api/v2/login/idp/.

To add an identity provider

Admin panel

On the Projects and users screen, click the required domain.
Switch to the Settings > Identity provider screen, and then click Add.
In the Add identity provider window, specify the following parameters:
1. A custom name of the identity provider that will be shown on the login screen.
2. The unique issuer ID provided by the OIDC provider. It usually appears as a URN.
3. The client identifier and secret to access the OIDC provider.
4. The metadata URL of the OIDC provider's discovery endpoint. The metadata URL is typically the issuer endpoint concatenated with the path /.well-known/openid-configuration. For example, if the issuer ID is https://idp.example.com/adfs/, the metadata URL will be https://idp.example.com/adfs/.well-known/openid-configuration.
5. Scopes that define what user identity data will be shared by the OIDC provider during authentication.
  
  The scopes allatclaims and openid are mandatory for Microsoft AD FS providers.
In the Mapping section, you can either create mapping rules manually or automatically from a mapping file:
- To manually create mapping rules
  1. Select Create mapping rules, and then click Add.
  2. In the Add rule window, create Mapping conditions by clicking Add and specifying the required parameters:
    
    In Attribute, specify a user attribute that you obtain from the identity provider during authentication.
    
    In Condition, specify a condition to apply to the attribute. With the condition Exists, all users with this attribute will be mapped. The condition Contains maps users if this attribute contains any of the specified values. The condition Does not contain maps users if this attribute does not contain any of the specified values.
    
    In Value, specify the desired attribute value as a string, comma-separated list, or regular expression.
  3. Select an existing domain group to assign federated users to.
  4. If you have a mapping rule with the condition Exists, select attributes that the name of a local user will consist of. For example, with the mapping attribute email and mapping condition Exists, names of local users may be composed of their emails.
- To automatically create mapping rules
  1. Select Upload a mapping file in the JSON format with already configured mapping rules.
  2. Write mapping rules in the JSON format in the Mapping data field. Alternatively, click Upload, and then browse a JSON file on your local server to load the mapping data from.
    
    A mapping file may look as follows:
    # cat mapping.json [ { "local": [ { "user": { "name": "{0}" }, "group": { "name":"users" } } ], "remote": [{"type": "email"}] } ]
    
    In this example, all users that have the attribute email will be mapped to the group users within the default domain. For details on creating a mapping file, refer to the OpenStack documentation.
Click Add.

Command-line interface

Use the following command:

vinfra domain idp create --domain <domain> --issuer <issuer> --scope <scope>
                         [--metadata-url <metadata-url>] [--client-id <client-id>]
                         [--client-secret <client-secret>] [--mapping <path>]
                         [--enable] [--disable] <name>

--domain <domain>

Domain name or ID

--issuer <issuer>

Identity provider issuer

--scope <scope>

Scope that define what user identity data will be shared by the identity provider during authentication.

The scopes allatclaims and openid are mandatory for Microsoft AD FS providers.

--metadata-url <metadata-url>

Metadata URL of the identity provider's discovery endpoint

--client-id <client-id>

Client ID to access the identity provider

--client-secret <client-secret>

Client secret to access the identity provider

--mapping <path>

Path to the mapping configuration file.

A mapping file may look as follows:

# cat mapping.json
[
    {
        "local": [
            {
                "user": {
                    "name": "{0}"
                },
                "group": {
                    "name":"users"
                }
            }
        ],
        "remote": [{"type": "email"}]
    }
]

In this example, all users that have the attribute email will be mapped to the group users within the default domain. For details on creating a mapping file, refer to the OpenStack documentation.

--enable

Enable identity provider

--disable

Disable identity provider

<name>

Identity provider name

For example, to add an identity provider with the name My ADFS within the mydomain domain, run:

# vinfra domain idp create --domain mydomain --issuer https://idp.example.com/adfs/ \
--scope "allatclaims openid email" --client-id xxx --client-secret xxx --mapping mapping.json "My ADFS"

The added identity provider will appear in the vinfra domain idp list output:

# vinfra domain idp list --domain mydomain
+-------------+---------+-------------------------------+--------------------------+-----------+
| id          | name    | issuer                        | scope                    | domain_id |
+-------------+---------+-------------------------------+--------------------------+-----------+
| df5a54ce<…> | My ADFS | https://idp.example.com/adfs/ | allatclaims openid email | 36f454<…> |
+-------------+---------+-------------------------------+--------------------------+-----------+