Confluent Cloud - Configuration Guide¶
Introduction¶
This configuration guide documents how to install the KaaS applications on Confluent Cloud.
Abbreviations and definitions¶
See Abbreviations and definitions.
Service Account for Terraform¶
Account Creation¶
- Open Confluent Cloud with an admin account
- Open Accounts & access in the menu
- Open Service Accounts
- Click + Add Service Account
- Set following values Name: tf_runner Description: tf_runner click Next
- Select Novo Nordisk A/S
- Click + Add role assignment
- Select OrganizationAdmin and click Add
- Select Review
- Create Service Account
API Key creation¶
- Open Confluent Cloud with an admin account
- Open Accounts & access in the menu
- Click + Add key
- Select Granular access
- Select Existing account tf_runner
- Click Next
- Set following in Description tf_runner
- Download and continue.
- Save API key info from text file in PIM
SSO¶
SSO Account Creation in Entra AD (formerly Azure AD)¶
- Create ServiceNow ticket for SSO creation
| Name | Parameter |
|---|---|
| Name | KaaS |
| Protocol Used | SAML2 |
| Identifier (Entity ID) | urn:auth0:confluent:novo-nordisk-hq |
| Reply URL | https://login.confluent.io/login/callback?connection=novo-nordisk-hq |
| Sign-on URL | https://confluent.cloud/login/sso/novo-nordisk-hq |
| Relay State | N/A |
| Logout URL | https://login.confluent.io/logout |
| Claim Attributes | (default) |
| Unique User Identifier | user.principalname |
| groups | user.groups |
| User and Group | Add all AD Groups on the platform |
| Type | Manual |
| SCIM Information(Only for Automatic Assignments) | N/A |
SSO Setup in Confluent Cloud¶
- Open Confluent Cloud with an admin account
- Open Single sign-on in the menu
- Create Single sign-on
- Set following in SSO identifier novo-nordisk-hq
- Click Next
- Upload signing Certificate from AzureAD
- Set following in SAML sign-in URL https://login.microsoftonline.com/fdfed7bd-9f6a-44a1-b694-6e39c468c150/saml2
- Set following in Email mapping http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
- Set 'User Group permissions', SAML attribute to http://schemas.microsoft.com/ws/2008/06/identity/claims/groups
- Click Submit
Fallback Account for SSO¶
Account Creation¶
- Open Confluent Cloud with an admin account
- Open Accounts & access in the menu
- Open User Accounts
- Click + Add User
- Set following values email address: Use local authentication for this user: true select Continue
- Select Novo Nordisk A/S
- Click + Add role assignment
- Select OrganizationAdmin and click Add
- Select Confirm
SSO Setup for Confluent Support Portal¶
Link to the Confluent Cloud Documentation: Manage SSO Access to Confluent Support Portal on Confluent Cloud
Steps to be executed: - Open Confluent Cloud UI with Platform Admin role. - Navigate to "Organization Settings". - Under the "Trusted Domains" section, click "Add Domain". - Enter the domain name "novonordisk.com" as a trusted domain, then click "Create domain and continue". - Select verification method as "DNS TXT Record". Further instructions would be displayed here. - Before proceeding with the domain verification step, a DNS entry needs to be added on the Novo Nordisk side. For this, submit a ServiceNow request for DNS record creation, with the following details: - Action : Create - Full DNS Name : novonordisk.com - Type : TXT - Value : confluent-verification=6a454465-7ae0-48a8-90df-2719216e6660 (This value is to be copied from the Confluent Cloud UI) - Location : Internal and Public - Once the ServiceNow request is processed, navigate back to the "Organization Settings", and under "Trusted Domains" section, click "Verify domain".
Links for reference: - ServiceNow Request submitted for DNS record creation: RITM0769443 - Confluent Support ticket submitted for clarification of queries: 239301
Manage TLS protocols¶
By default, all Kafka clusters on Confluent Cloud use TLS 1.2. For dedicated clusters only, you can enable TLS 1.3 by updating the Kafka broker configuration property for the Kafka cluster. For all dedicated clusters on the KaaS platform, both TLS 1.3 and TLS 1.2 are enabled.
These settings were modified using REST API calls as per Confluent documentation.