Access Token for .Net Proxy

Configure an access token to connect to a .NET proxy service.

Figure: .NET Proxy Access Token Configuration screen

Dot NET Proxy Access Token Configuration screen

Background and Setup

Prerequisites

  • A valid web service — for example a live, valid WSDL file.

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 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 Google Drive 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 application 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?

  • 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 Name Definition

Token Name

Function:
Specifies the unique name for your connection to the .NET proxy.
Accepted Values:
A text string that can have letters, numbers, and 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

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.

Load Assembly

Function:
Gets a list of available assemblies to select in the Assembly field.

Assembly

Function:
Specifies the .NET assembly to connect to a web service.
Accepted Values:
A valid assembly from the list.
Default Value:
None

User Name

Function:
Specifies the user name for the .NET proxy service.
Accepted Values:
A valid user name.
Default Value:
None

Domain

Function:
The authentication domain for the .NET proxy service.
Accepted Values:
One line of text with no spaces.
Default Value:
None

Password

Function:
The password for the authentication account.
To Open this Field:
Do one of these:
  • Click Exchange Server 2007 > Custom User.
  • Click Exchange Server 2010/2013 > Custom User.
  • Click Microsoft 365 > Basic.
Accepted Values:
An alphanumeric string that represents a password.
Default Value:
None
Limitations:

Custom Header

Function:
Specifies the custom headers required for the web service.
Accepted Values:
A valid custom header for the web service.
Default Value:
None

Test Connection

Function:
Makes sure the specified .NET proxy connection 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
Limitations:
  • This field was removed from the UI in AgilePoint NX OnPremises and Private Cloud v7.0 Software Update 2. Access token credentials are encrypted by default. If you want to store credentials in unencrypted format, contact AgilePoint Customer Support.