Creating an extension

Build secure integrations and custom solutions that extend the capabilities of your OpenText Core applications.

Creating an extension allows you to securely connect platforms, integrations, and automations to your OpenText Core application. The extension application serves as the trusted identity that authenticates with OpenText services and accesses APIs on behalf of your solution.

Public Cloud tools:

Process Overview

This overview guides you through the process of creating an extension application with Thrust Studio; the full detailed documentation is available here.

Create an Extension

  • Establish a trusted application identity that represents your extension, integration, or custom solution within the OpenText Cloud platform. The extension application acts as the foundation for all subsequent authentication and API interactions.
  • Outcome: An extension application is registered in your organization and is ready to be configured for secure access to OpenText APIs.

Generate Application Credentials

  • Enable your extension application to prove its identity when communicating with OpenText services. Credentials are used to establish trust between your application and the platform and form the basis for secure authentication. 
  • Outcome: Your application has the credentials required to authenticate, obtain access tokens, and securely access OpenText APIs

Authentication and API Access

Creating an extension application establishes your application's identity, but additional authentication components are required before it can access OpenText APIs. 

Service Client

A service client represents the application when it communicates with OpenText services. It is associated with the extension application and uses generated credentials to authenticate requests. 

  • OpenText services need a trusted way to identify which application is making a request.
  • Outcome: Your application has a secure identity that can be used to request access to OpenText APIs. 

Authenticate API Access

Before calling an API, the service client must authenticate using its assigned credentials. This authentication process verifies the application's identity and determines the permissions it has been granted. 

  • Authentication protects tenant data and ensures only authorized applications can access OpenText services.
  • Outcome: The service client is authorized to request access tokens for API operations.

Request an Access Token

Once authenticated, the service client requests an access token from the authorization service. The access token is included with subsequent API requests and represents the approved permissions of the application. 

  • Access tokens provide a secure, time-limited mechanism for accessing APIs without exposing application credentials in every request.
  • Outcome: Your application receives a valid access token and can successfully call OpenText APIs to access data, automate processes, and build extensions.

Develop and Test Your Integration

Use OpenText APIs and services to build extensions with Thrust Studio, automate business processes, integrate external systems, or create new capabilities that enhance your Core SaaS applications.

  • This stage focuses on implementing and validating your solution using the authenticated application identity established in the previous steps. 
  • Outcome: A working extension or integration that can securely interact with your OpenText SaaS environment and deliver business value through automation, integration, or custom functionality.

Further guidance for managing your extension, Organization account, service clients, inviting colleagues, and more can be found in the Admin Center documentation.