Access Token for Active Directory

Configure an access token to connect to Active Directory.

Screen



Background and Setup

Good to Know

  • In most cases, you can use a global access token or an application level access token:
    • Global access tokens are shared across all users and applications. If you want all process designers and form 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 form users for a particular application should access an external system — for example, a Google Drive account that is only used to share files within a small team.
  • Access tokens are used to connect AgilePoint NX applications to external data sources. Windows Azure Active Directory can be used for access tokens, but it can also be used as an authentication provider for the AgilePoint NX Portal. Access tokens cannot be used to authenticate to the Portal.

    For more information about configuring authentication providers, refer to Add an Authentication Type.

  • Documentation for Integrations with Third-Party, External, or Open Source Technologies

    The highest priority for AgilePoint NX Product Documentation is accuracy. Whenever feasible, AgilePoint provides input details, business rules, or example values for third-party integrations. These can include any technology that is not native to AgilePoint NX, such as Salesforce, Active Directory, or REST. However this information is subject to change without notice to AgilePoint. Because we can not guarantee the accuracy of this information, the details provided for third-party product input values, as well as examples for third-party product integrations, are limited in the AgilePoint documentation. It is the responsibility of third-party vendors to provide documentation related to these aspects of their software and services.

    For examples of use case implementations or configuration field input values for third-party products, AgilePoint recommends these resources:

    • AgilePoint Community Forums - An AgilePoint-moderated, crowd-sourcing user forum where you can ask questions about specific techniques, the solutions to use cases, workarounds, or other topics that may not be covered in the Product Documentation.
    • Professional Services - If you can not find the information you need for your specific business problem, mentoring is available through AgilePoint Professional Services.
    • Personalized Training - AgilePoint can provide personalized training for your organization. To request personalized training, contact AgilePoint Sales.
    • Third-Party Vendor Documentation - Whenever feasible, AgilePoint provides links to third-party vendor documentation.

      This does not include technology standards or protocols, such as JavaScript, REST, or FTP. Resources for these technical standards are publicly available on the Internet.

Fields

Field Name Definition

Token Name

Function:
Specifies the unique name for your connection to Active Directory.
Accepted Values:
A text string that can include letters, numbers, and spaces
Default Value:
None

Description

Function:
A description for your access token.
Accepted Values:
More than one line of text.
Default Value:
None
Example:
Refer to:

User Account

Function:
Specifies the user account to connect to Active Directory.
Accepted Values:
Default Value:
Custom User

Context Domain

Function:
Specifies the name of your Active Directory domain.
To Open this Field:
  1. On the Active Directory access token screen, select Custom User.
Accepted Values:
A valid Active Directory domain name.
Default Value:
None

User Name

Function:
Specifies the user name of the account to use to create a group in Active Directory.
To Open this Field:
  1. On the Active Directory access token screen, select Custom User.
Accepted Values:
A valid user name.
Default Value:
None
Accepts Process Data Variables:
No

Password

Function:
Specifies the password of the account to use to create a group in the domain
To Open this Field:
  1. On the Active Directory access token screen, select Custom User.
Accepted Values:
An alphanumeric string that represents a password.
Default Value:
None
Accepts Process Data Variables:
No

Directory Type

Function:
Specifies the format for your Active Directory.
Accepted Values:
  • LDAP - Specifies your Active Directory uses LDAP.
  • WinNT - Specifies your Active Directory uses WinNT.
Default Value:
LDAP

Directory Address

Function:
Specifies a host address for your Active Directory.
To Open this Field:
  1. On the Active Directory access token screen, select Custom User.
Accepted Values:
  • IP address - The IP address of the Active Directory. For example, 211.325.5.3.
  • IP address/[relative distinguished name (RDN)] - The IP address of the Active Directory with the container name (CN), organizational unit (OU), or both for the user. For example, 211.325.5.3/OU=MyGroup
Default Value:
None

Directory Port

Function:
Specifies a port number of the Active Directory.
To Open this Field:
  1. On the Active Directory access token screen, select Custom User.
Accepted Values:
A valid port number for your Active Directory.
Default Value:
389

Test Connection

Function:
Makes sure the specified Active Directory account is correct.

Encrypt

Function:
Stores the access token in the AgilePoint database as encrypted data.
Note: AgilePoint recommends you to store this access token in the database in encrypted format.
Accepted Values:
  • Deselected - The access token is in plain text in the database.
  • Selected - The access token is encrypted in the database.
Default Value:
Selected