Skip to end of banner
Go to start of banner

Application Configuration in Azure Portal for OAuth2 Account to use in Kafka

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

In this Article

Overview

Snaps in the Kafka Snap Pack require a Kafka OAuth2 account to access Azure resources. To authorize the accounts successfully, ensure that you create and configure two applications corresponding to the account:

  • Confluent Cloud application

  • Client application

Prerequisites

An Azure account with a free subscription to create the application.

Key Steps in the Workflow

Create two Applications in the Azure Portal

  1. Log in to the Microsoft Azure Portal.

  2. Navigate to Azure services > Microsoft Entra ID.

  3. Navigate to Add > App registration.

  4. On the Register an application page, specify the name for registering the Confluent Cloud application, which allows client applications to claim roles in Confluent Cloud, and click Register. Learn more about creating an application at https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app.

To use an existing application, navigate to Portal Home > Azure Active Directory > App registrations > All applications. In the search box, specify the application name you want to use. The details of the registered application are displayed in the search list.

This application does not need the Redirect URI.

essential-details.png

  1. Click on Add an Application ID URI, which is used by the client applications to identify this application.

  2. Set the Application ID URI.

  3. Navigate to Go to App roles.

    1. Click on Create app role.

    2. Set up a Dev Admin role.

    3. Choose Applications for the Allowed member types.

    4. Specify the Value as dev.environmentAdmin.

    5. Provide a useful description of what this role is supposed to allow.

      create-app-role.png

  4. Navigate to Manifest in the left navigation to ensure Azure Active Directory returns version 2 tokens on its token endpoint.

    manifest-3.png

    1. Search for the key for ‘accessTokenAcceptedVersion’.

    2. Update the value from null to 2, and save it.

      manifest-2.png

  5. Return to Overview and view the Endpoints, where you can copy and save the OAuth 2.0 token endpoint.

    endpoints.png

  6. Register the Kafka client application.

    client-app-registration.png

  7. Navigate to Certificates & secrets on the left navigation bar and create a new client secret.

You can copy the Client secret value only after it is generated. Note that this value is displayed only once, so ensure to copy it securely.

client-secret-client-app.png

  1. Navigate to the API permissions tab on the left navigation and select Add a permission. Then, select the APIs my organization uses option.

    request-api-permissions-0.png

  2. Add the roles to your client application according to your Confluent Cloud registration.

    request-api-permissions.png

  1. Copy and save the Scope parameter from the role you added to the client application.

    scope-parameter.png

  2. Click the Grant admin consent and confirm the grant. This completes the Azure AD configuration for the client application. You can now generate a JWT from an Azure AD OAuth 2.0 token endpoint using the Client ID, Client Secret, and Scope Parameters.

    grant-permission.png

Specify the Credentials And Validate the Snap account

  1. Navigate to the Kafka Snap of your choice and configure the Kafka OAuth2 Account with the details from the Azure portal's registered application.

    kafka-oauth2-config.png

  2. Validate the Snap Account.

Related Content

  • No labels

Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.