Integrations

AVEVA CONNECT provides an Integrations framework that enables external applications, tools, and services to authenticate and interact securely with CONNECT services, including the AVEVA Integration Service (AIS).

Integrations are managed by an Account Administrator from the CONNECT portal.

CONNECT supports the following integration types:

Access tokens

An Access Token is an authorisation passcode generated from the CONNECT portal. It allows external applications or tools that are not natively integrated with CONNECT to authenticate and interact with CONNECT services.

Access Tokens can be scoped at two levels:

Key capabilities:

• Set required access level and user permissions

• Define an expiration date for the token

• Generate, clone, and revoke tokens as needed

  Note: AVEVA products internally generate a CONNECT token when integrating with the AIS Cloud service. Manually generating Access Tokens is generally not recommended unless required for external tools or custom integrations.

Applications

An Application in CONNECT allows an on-premises application to authenticate using CONNECT's single sign-on (SSO) capability.

When an application is registered, CONNECT automatically generates a Client ID - a unique identifier used by the application to authenticate against CONNECT services.

• Up to five applications can be registered per CONNECT account.

• Applications can be created, edited, and deleted by the Account Administrator.

Service applications

A Service Application is designed for machine-to-machine (M2M) authentication, where no user interaction is involved.

It uses a Client ID and Client Secret (OAuth 2.0 Client Credentials flow) to authenticate and obtain an access token programmatically.

AIS support for CONNECT integrations

AVEVA Integration Service supports the following CONNECT integration types: