> For AI agents: [llms.txt](https://docs.trustedauth.com/llms.txt) provides a Markdown index of this documentation.

# Confluent Cloud

Confluent Cloud is a fully managed, cloud-native event streaming platform powered by Apache Kafka. See <https://www.confluent.io/>. You can configure your Confluent Cloud account for Single Sign-On (SSO) through Identity as a Service.

note

This procedure was tested using previous versions of Identity as a Service 5.34 and Confluent Cloud Trial version 7.2. Other versions of Confluent Cloud may require integration and configuration steps that differ from those documented in this procedure. For newer versions of Confluent Cloud, use this procedure as a starting point for integrating Confluent Cloud. In the event of other issues, contact <support@entrust.com> for assistance.

Before you begin, open two browser windows. In one window, log in to your Confluent Cloud administrator account. In the other window, log in to your IDaaS administrator account.

To integrate Confluent Cloud with Identity as a Service, you must do the following:

## Step 1: Copy the Assertion consumer URL and the Entity ID from Confluent Cloud

1. Log in to your Confluent Cloud administrator account. The **Confluent Cloud** home page appears.
2. Click the menu icon and select **accounts and access**. The **Accounts & access** page appears.
3. Click the **Single sign-on** tab.
4. Click **Enable SSO**. The **Single sign-on** page appears.
5. In the **SSO identifier** field, enter the SSO identifier. For example, sso-entrust.
6. Click **Next**. The **Single sign-on** page appears.
7. Open a text editor such as Notepad and copy and save the following:
   - Assertion consumer URL
   - Entity ID
8. Click **Next**. The **Single sign-on Configure SSO settings** page appears.
9. Leave the **Single sign-on Configure SSO settings** page open. You return to this page in _Step 3: Add the IDaaS metadata to Confluent Cloud_.

## Step 2: Add Confluent Cloud to Identity as a Service

1. In Identity as a Service, click Menu icon **>** **Security > Applications**. The **Applications** **Lists** page appears.
2. Click **Add**. The **Select an Application Template** page appears.
3. Do one of the following:
   - Select **SAML Cloud Integrations** from the search drop-down list and scroll to find the application you want to add to IDaaS.
   - In the **Search bar**, enter a search option to filter for the application you want to add to IDaaS.
4. Click **Confluent Cloud**. The **Add Confluent Cloud** page appears.
5. Enter an **Application Name**.
6. Enter an **Application Description**.
7. Optional. Add a custom application logo.
   1. Click Plus icon next to **Application Logo**. The **Upload Logo** dialog box appears.
   2. Click Upload icon to select an image file to upload.
   3. Browse to select your file and click **Open**. The **Upload Logo** dialog box reappears showing your selected image.
   4. If required, resize your image.
   5. Click **OK**.
8. Select the **Authentication Flow** that appears to users during login.
9. Click **Next**. The **General** page appears.
10. In the **Default** **Assertion Consumer Service URL**, enter the **Assertion Consumer Service URL** you copied in _Step 1: copy the Assertion Consumer Service URL and Entity ID from Confluent Cloud_.
11. In the **Service Provider Entity ID** field, enter the **Entity ID** you copied _Step 1: copy the Assertion Consumer Service URL and Entity ID from Confluent Cloud_.
12. Leave the **Single Logout Service URL** field empty.
13. Enter the **SAML Session Timeout** to the time when the SAML Assertion times out. The maximum is 720 minutes.
14. Enter the **Max Authentication Age (seconds)** to set the maximum amount of time that can elapse before a user is required to reauthenticate during a new login attempt. This applies for both SP-initiated and IDP-initiated login. Set this field to -1 to disable this feature.
15. From the **SAML NameID Attribute** drop-down list, select **Email**.
16. From the **SAML NameID Encoding Format** drop-down list, select **Email**.
17. From the **SAML Signing Certificate** from the drop-down list, select the SAML Signing Certificate.
18. Optional: Select **Respond Immediately for Unsuccessful Responses** to return to the application immediately after a login failure, rather than allow user to try again with a different userID.
19. Deselect **Enable Go Back Button** if you do not want users to be able to go back to the Confluent login page to log in.
20. Select **Show Default Assertion Consumer URL Service in the My Profile**. When selected, the Default Assertion Consumer URL appears in a user's My Profile page in addition to relay states and Alternative Assertion Consumer URLs.
21. Add **SAML attributes** as follows:
    1. Add the **First Name** attribute, as follows:
       1. Under **SAML Attributes**, click **Add**. The **SAML Attributes** dialog box appears.
       2. In the **Name** field enter Email
       3. Click **Add** next to **Value(s)**.
       4. In the **Values** field, type `<` and select **Email**.
       5. Click **Add**.
       6. Leave the remaining settings at the default values.
22. Click **Submit**.

## Step 3: Add a resource rule

See [Create resource rules](/docs/authentication-and-security/create-and-manage-resource-rules.md).

## Step 4: Download the metadata from Identity as a Service

Download the Metadata file from Identity as a Service

1. In Identity as a Service, click Menu icon **>** **Security > Applications**. The **Applications List** page appears.
2. Do one of the following:
   - Click Cloud Download icon next to the application you are integrating with Identity as a Service.
   - Click Ellipsis Vertical icon next to the application you are integrating with Identity as a Service and select **SAML IDP Metadata**.
3. The **SAML Application Metadata** dialog box appears.
4. **Select the certificate to include in the SAML IDP Metadata file** from the drop-down list.
5. If applicable, **Select the domain to include in the SAML IDP Metadata** file from the drop-down list.
6. Enter the **Lifetime, in days, for the SAML IDP Metadata file**. The value must be between 2 and 730.
7. Do one of the following, as required:
   - Copy the **Public Endpoint** to paste into your SAML application being used Identity Provider authentication.
   - Click **Download**.

note

If you are using multiple domains, you must download each domain's metadata file separately because the values in the metadata file vary for each domain.

## Step 5: Add the IDaaS metadata to Confluent Cloud

1. Return to the page you left open in _Step 1: Copy the Assertion consumer URL and the Entity ID from Confluent Cloud_.
2. On the **Single sign-on Configure SSO settings** page, select **Upload**.
3. Browse to upload the metadata you copied from _Step 6: Download the metadata from Identity as a Service_.
4. Select **Email mapping** from the attribute mapping drop-down list.
5. Click **Submit**.

## Step 6: Test the integration

### Testing Service Provider Login

1. Open a Web browser and enter the URL for your Confluent account.
2. Click **Login**. You are redirected to the Confluent Cloud login page.
3. Enter the Confluent Cloud account email address. Click **Single sign-on**.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to Confluent Cloud.

### Testing Identity as a Service redirect log in

1. Log in to your Identity as a Service account.
2. Go to your **My Profile** page if you are not already there.
3. Under **Applications**, click **Confluent Cloud**.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to Confluent Cloud.