Access Token for PostgreSQL

Configure an access token to connect to PostgreSQL.

Figure: PostgreSQL Access Token Configuration screen

PostgreSQL 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 the 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
Function:
Specifies the unique name for your connection to PostgreSQL.
Accepted Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None

Description
Function:
A description for your access token.
Accepted 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.

Database Server Name
Function:
Specifies the host name or IP address of the PostgreSQL server where your database is installed.
To Open this Field:
  1. On the PostgreSQL Access Token screen, click Quick Config.
Accepted Values:
A host name or IP address for your PostgreSQL server.
Default Value:
None
Accepts Process Data Variables:
No
Limitations:

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?

Example:
  • 192.168.112.139
  • postgresql.mydomain.com

Database Name
Function:
Specifies the name of the database to which to connect in PostgreSQL.
To Open this Field:
  1. On the PostgreSQL Access Token screen, click Quick Config.
Accepted Values:
The name of a database in your PostgreSQL environment.
Default Value:
None
Limitations:

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?

Port
Function:
Specifies the port number to connect to the PostgreSQL server.
To Open this Field:
  1. On the PostgreSQL Access Token screen, click Quick Config.
Accepted Values:
A valid port number.
Default Value:
None
Accepts Process Data Variables:
No

Timeout (Seconds)
Function:
Specifies the maximum time in seconds to connect to the PostgreSQL server.
To Open this Field:
  1. On the PostgreSQL Access Token screen, click Quick Config.
Accepted Values:
An integer.
Default Value:
600

SSPI (Integrated Security)
Function:
Determines whether the SSPI integrated security is to be activated.
To Open this Field:
  1. On the PostgreSQL Access Token screen, click Quick Config.
Accepted Values:
  • Deselected - Specifies not to activate the SSPI integrated security.
  • Selected - Specifies to activate the SSPI integrated security.
Default Value:
Deselected

User Name
Function:
Specifies the user name for PostgreSQL authentication.
To Open this Field:
  1. On the PostgreSQL Access Token screen, click Quick Config.
Accepted Values:
The user name for your PostgreSQL account.
Default Value:
None
Accepts Process Data Variables:
No

Password
Function:
The password for the authentication account.
To Open this Field:
  1. On the PostgreSQL Access Token screen, click Quick Config.
Accepted Values:
An alphanumeric string that represents a password.
Default Value:
None
Accepts Process Data Variables:
No

Connection String
Function:
Specifies the connection string to authenticate to the PostgreSQL server.

The connection string comes from PostgreSQL.

To Open this Field:
  1. On the PostgreSQL Access Token screen, click Manual.
Accepted Values:
One line of text (a string) that can have letters, numbers, spaces, and special characters.
Default Value:
None
Example:
User ID=admin;Password=mypassword;Host=192.186.121.193;Port=5432;Database=sales;

Test Connection
Function:
Makes sure the specified PostgreSQL credentials are correct.