Access Token for Apache Kafka

Configure an access token to connect to Apache Kafka.

Figure: Apache Kafka Access Token Configuration screen

Apache Kafka Access Token Configuration screen

Background and Setup

Prerequisites

Good to Know

  • In most cases, you can use a global access token or an app level access token:
    • Global access tokens are shared across all users and apps. If you want all process designers and runtime app users in your AgilePoint NX tenant to be able to connect to an external data source, use a global access token. An example is a SharePoint site on an intranet that all employees in a company can access.
    • Application level access tokens are shared with all processes in a process-based app, or restricted to use within a form-based app. Use application level access tokens if only process designers or runtime app users for a particular application should access an external system — for example, a Box account that is only used to share files within a small team.
  • Access tokens are collections of credentials that are used to authenticate communication directly between AgilePoint NX and an external system. Because it is the AgilePoint NX system that uses these credentials, rather than an app, there is no difference between design time and runtime access tokens. Access tokens are never checked in or published, and they do not use version control. If you change an access token in App Builder or Manage Center, the access token changes immediately everywhere the access token is used. Changes to app level access tokens apply to all versions of an app, including running application instances. Changes to global access tokens apply everywhere they are used in AgilePoint NX. You can not roll back an access token to a previous version.

    For more information, refer to What Data Is Deleted When I Delete an App or Application Resource?

  • This screen may look different in different places. The UI varies for this screen depending upon how you open it. However, the fields for this screen are the same in all places.
  • Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Fields

Field NameDefinition

Token Name

Description:
Specifies the unique name for your connection to Apache Kafka.
Allowed Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Description:
A description for your access token.
Allowed Values:
More than one line of text.
Default Value:
None
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Bootstrap Server URL

Description:
Specifies the Apache Kafka server URL.
Allowed Values:
A server URL for Apache Kafka.
Default Value:
None
Example:
pkc-6ojv2.us-west4.gcp.confluent.cloud:9092

On Premises / Cloud

Description:
Specifies the type of environment where the Apache Kafka server is hosted.
Allowed Values:
  • On Premises - Connects to Apache Kafka server in an on premises environment.
  • Cloud - Connects to Apache Kafka server in a cloud environment.
Default Value:
On Premises

Connection Type

Description:
Specifies the authentication type to connect to Apache Kafka.
To Open this Field:
  1. On the Apache Kafka Access Token screen, click On Premises.
Allowed Values:
  • PLAINTEXT - Uses a server URL to connect to Apache Kafka.
  • SASL/PLAINTEXT - Uses the specified user credentials to connect to Apache Kafka.
Default Value:
PLAINTEXT

User Name

Description:
Specifies the user name for Apache Kafka authentication.
To Open this Field:
  1. On the Apache Kafka Access Token screen, click On Premises.
  2. In the Connection Type field, select SASL/PLAINTEXT.
Allowed Values:
The user name for your Apache Kafka environment.
Default Value:
None

Password

Description:
The password for the authentication account.
To Open this Field:
  1. On the Apache Kafka Access Token screen, click On Premises.
  2. In the Connection Type field, select SASL/PLAINTEXT.
Allowed Values:
An alphanumeric string that represents a password.
Default Value:
None

API Key

Description:
Specifies the API key to call the Apache Kafka service.
To Open this Field:
  1. On the Apache Kafka Access Token screen, click Cloud.
Allowed Values:
An API key from Apache Kafka.
Default Value:
None

API Secret

Description:
Specifies the API secret to call the Apache Kafka service.
To Open this Field:
  1. On the Apache Kafka Access Token screen, click Cloud.
Allowed Values:
An API secret from Apache Kafka.
Default Value:
None

Test Connection

Function:
Makes sure the specified Apache Kafka credentials are correct.