IBM Cloud Pak SCIM Azure AD integration

From foundational services version 3.19.9, 3.23, and later, Cloud Pak can use the Azure-IM integration by using SCIM to manage the users and groups at the CloudPak end. The Azure-IM integration will also help in managing the authentication and authorization for the resources.

Azure Active Directory (Azure AD) is an enterprise identity service that provides single sign-on, multifactor authentication, and conditional access to protect against cybersecurity attacks.

The image shows process diagram for azure SCIM integration

Configuration required for Azure integration using SSO/SAML and SCIM

See the following notes:

See the following prerequisites:

Follow the steps in sequence:

  1. Create Azure Org if you have not created the Azure Org. And, deploy the foundational services version 3.19.9, 3.23, and later.
  2. Create the SCIM app and configure the app at Azure. For more information, see Configure CloudPak as SAML service provider (SP) at Azure.
  3. Set up single-sign-on with SAML.
  4. Register Azure SAML IdP at Cloud Pak. For more information, see Configure Azure as SAML IdP at CloudPak.
  5. Perform SCIM provisioning for Azure users and groups. For more information, see Manage users and Manage groups.
  6. Login or onboard to the Cloud Pak.

The image shows high-level process diagram for Azure

Primarily, the following main configurations are required to get Azure SCIM Integration working with CloudPak along with SAML SSO.

Configuring Cloud Pak as SAML SP at Azure and configuring Azure as SAML IdP at Cloud Pak are performed to make the e2e SSO work. And, configuring SCIM integration with CloudPak SCIM server is performed to enable SCIM provisioning.

Configure Cloud Pak as SAML service provider (SP) at Azure

Before you begin: You must have the SP, CloudPak CommonServices IM liberty SAML metadata. You can use the samlmetadata API to get the SAML metadata. For more information, see SAML metadata export by using samlmetadata API.

Steps

  1. Login to Azure org. Azure home page appears.
  2. In the home page, select Manage Azure Active Directory by clicking View.
  3. In Default Directory page, click Enterprise applications in Manage section. The Enterprise applications page appears.
  4. Select the enterprise application from the list in Enterprise applications page.

  5. Select Set up single sign on by clicking Get started.

    The image shows Azure dashboard

  6. Select Upload metadata file option and upload the SP metadata file and click Add.

    The image shows SP metadata

  7. Confirm the Attributes & Claims names and values.

    The default User attributes:

    Note: While registering the Azure IdP, you can use the same default keys of the Name field to specify the values in the token_attribute_mappings section. The values allows Azure to send the attributes in SAML response to Cloud Pak. In case, you have customized the attributes keys, use the customized keys only to specify the values in the token_attribute_mappings section. For more information, see SAML authentication with Azure Active Directory. For example, if you are using the default attributes keys to specify the values in token_attribute_mappings section:

       "token_attribute_mappings": {

      "sub": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name",
      "given_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname",
      "family_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname",
      "groups": "http://schemas.microsoft.com/ws/2008/06/identity/claims/groups",
      "email": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress",
      "first_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname",
      "last_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname"
   }

  8. Once the metadata is saved, go to the SAML certificate section and download Federation Metadata XML and save as idp-metadata-xml.xml.

  9. Click Test this application.

  10. Verify the login by clicking Test single sign-on with cpd-ad section.

  11. Go to SCIM app and assign the user and/or group who are required to login at Cloud Pak end. To assign the user and/or group:

    • Under Manage section, select Enterprise applications from the menu. The Enterprise applications page appears.
    • Select Assign users and groups. Then, select the users and groups that you want to assign.

If you want to assign existing LDAP users or group to the App, use Azure Active Directory (Azure AD) to create a domain in Azure and link the Azure AD to an on-premises AD domain. For more information, see Integrate on-premises AD with Azure. After this, the LDAP entities can be imported to Azure and it can be used for assignment.

Configure Azure as SAML IdP at Cloud Pak

Use the IdP V3 API to register Azure as SAML IdP. For now, the Azure registration is not supported through UI. Therefore, you need to perform the registration using API only. However, the process remains the same. For more information about the IdP v3 usage, see IdP V3 registration with Azure.

With the registration IdP v3 API, the required Oauth client is also created. This Oauth client will be used for configuring SCIM server Oauth authentication from Azure.

Note: Provide the redirect_uri for oauthClient registration.

Upon successful registration, you will get clientId and clientSecret name. From the clientSecret, both the clientId and clientSecret can be retrieved.

To be concluded, the IdP v3 Azure registration does the following:

See the following prerequisites:

Steps

  1. Use the IdP V3 API to register Azure as SAML IdP.

    The following sample for Azure registration as SAML IdP. To get accessToken, see Get access token by using cpclient_credentials.

    curl --location --request POST 'https://cpconsoleroute/idprovider/v3/auth/idsource' \
--header 'Authorization: Bearer $accessToken' \
--header 'Content-Type: application/json' \
--data-raw
'{
   "name": "AzureSAML",
   "description": "AzureSAML",
   "protocol": "saml",
   "type": "azuread",
   "idp_config":
    {
      "token_attribute_mappings": {
        "sub": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name",
        "given_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname",
        "family_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname",
        "groups": "http://schemas.microsoft.com/ws/2008/06/identity/claims/groups",
        "email": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"
        "first_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname",
        "last_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname"
    },
      "idp_metadata": "Base64-encoded-metadata"
    },
    "jit": false,
    "scim_config":
    {
      "redirect_url": ["azure_redirect_url"],
        "scim_attribute_mappings": {
          "user":
          {
            "principalName": "userName",
            "name":
            {
              "givenName": "givenName",
              "familyName": "familyName"
            },
            "displayName": "displayName",
            "emails":
            [
            {
              "value": "emails",
              "type": "home"
            }
            ],
            "id": "id",
            "userName": "userName"
            },
            "group":
            {
             "principalName": "displayName",
             "id": "displayName"
             "displayName": "displayName"
            }
          }
      }
}'

  2. Upon successful registration, you might get the status similar to the following:

     {
    "status": "success",
    "message": "Identity provider {AzureSAML} is successfully registered with unique identifier : defaultSP, azureadclient created with clientId: yx3a5pwtdrmn0sf8ockyf97dg55lswo7 , client secret: azuread-oidcclient-secret"
 }

    The error message resembles the following:

      401 "error": "Insufficient user permission for role : rolename"
  400 "error": "schema error:schema validation error followed by error"
  400 "error": "duplicate : Idp with protocol=saml is already created"
  500 "error": "Other errors"

    token_attribute_mappings: token_attribute_mappings is a custom mapping that user can provide based on the SAML attribute mapping that is configured at Azure. User should modify the values, not the key, based on the Azure SAML attribute configuration. For more information about attributes, see Step 6 in Configure CloudPak as SAML service provider (SP) at Azure.

    scim_attribute_mappings: Provide the mapping attributes as in the CURL command. The defined mapping will be used in filter query, creating attributes and the response that is to be sent.

    Note: You can get the client credential details from the secret that has been created. This client credential details are sent back as a response.

To get the Oauth client credentials:

Once the registration is done, the SAML configuration can be validated by login through the cp-console directly. The default role will be Viewer.

For Platform UI SAML login, you need to first complete the Azure SCIM integration so that the provisioned user or group can be onboarded at Platform UI end. If you have not already completed the SCIM Integration and provisioned required for the users and groups, then complete the steps that are mentioned in Configure SCIM integration with CloudPak SCIM server before you proceed further.

To login Platform UI console, follow these steps:

  1. Onboard the user to Platform UI from the IM ScimServer. For example, azure_m1@vijayanjaygmail.onmicrosoft.com, a user that has been provisioned from Azure to IM SCIMServer. For more information, see steps that are mentioned in Configure SCIM integration with Cloud Pak SCIM server.

    Add users

    Add Azure users

  2. Once the user is onboarded, login to the Platform UI console with that user.

    CP console login

  3. Similarly, the provisioned group can also onboarded to Platform UI console from the IM ScimServer.

Onboarded to CPD console from IM ScimServer

Azure_dec is the member which is available inside groupdec.

Display Azuredec member

Member of the groups can login to the Platform UI console.

Member of groups in CPD console

Configure SCIM integration with CloudPak SCIM server

Note: You can follow this configuration process until the IM SCIM App is published to Azure AD app gallery. Later, you can use the proper Oauth configurations with clientID and clientSecret with the IBM Specific Integration App that has been created as a part of IdP V3 registration in Configure Azure as SAML IdP at Cloud Pak.

Steps

  1. Go to Azure Active Directory dashboard .
  2. Under Manage section, select Enterprise applications from the menu. The Enterprise applications page appears.

  3. Select the enterprise application from the list that is displayed on Enterprise applications page. Then, select Provisioning from the navigation menu.

    User provisioning

  4. Click Update credentials under Manage provisioning.

    Manage provisioning

  5. In Provisioning page, under Admin Credentials, provide Tenant URL and Secret Token.

    Tenant URL

    • Tenant URL: https://cpconsoleroute/idmgmt/identity/api/v1/scim

      Note: To get cpconsoleroute from cluster, see Getting the host details.

    • Secret token: Update the Secret Token as Oauth Bearer Token. To get the OAuth Bearer Token from cluster:

      • Login to OpenShift Container Platform cluster using oc CLI.

      • Run the following commands:

        oc get secrets/platform-auth-scim-credentials --template={{.data.scim_admin_password}} | base64 -D

        curl -k -X POST -H "Content-Type: application/x-www-form-urlencoded;charset=UTF-8" -d
"grant_type=password&username=scimadmin&password=passwordfromabove&scope=openid"
https://cpconsoleroute/idprovider/v1/auth/identitytoken --insecure

  6. Click Test Connection to test API Credential. For more information, see Validate a SCIM endpoint.

  7. Once the token is verified, follow the process to start provisioning for Managing users and Managing groups.

If you want to provision existing LDAP users or group to the app, follow the step to integrate on-premise AD with Azure.