OpenText Content Manager | EzeScan Help Center

Overview

This integrations provider browse, import, search and upload capabilities for OpenText Content Manager (OTCM). Formerly known as Micro Focus Content Manager, HP Content Manager, HP Records Manager, and HP TRIM.

Requirements

OpenText Content Manager server version 10.0 up to 25.3
- Service API feature must be installed
EzeScan WebApps 4.0.8 or higher

Connection

The connection to OTCM requires a Connector Instance be configured in Admin → Integrations. Use the Add New button to select OpenText Content Manager from the list of available connectors. Give the instance a name (e.g. CM PROD) and then fill in the below connection settings.

Option	Description
Server Base URL	The Service API base URL. This should be the OTCM server address with `/CMServiceAPI/` path suffix. For example: http://contentmanager/CMServiceAPI/
Authentication Type	The authentication type to use when connecting to the API. Supported options are: Basic OpenID Connect Windows
Impersonate User	Optional. Specify the user on whose behalf requests will be made to OTCM when authenticated as a service account. This feature is not supported when using OpenID Connect authentication.

Option

Description

Server Base URL

The Service API base URL.

This should be the OTCM server address with /CMServiceAPI/ path suffix.

For example:
http://contentmanager/CMServiceAPI/

Authentication Type

The authentication type to use when connecting to the API.

Supported options are:

Impersonate User

Optional. Specify the user on whose behalf requests will be made to OTCM when authenticated as a service account.

This feature is not supported when using OpenID Connect authentication.

Click the Test button to verify that the application can successfully connect to the server and authenticate your credentials.

Basic Authentication

Use basic credentials to authenticate with OTCM.

Option	Description
Username	The username used to log in to OTCM.
Password	The password for the specified user.

The {{username}} and {{password}} placeholders can be used to pass through the current EWA user credentials.

OpenID Connect Authentication

Authenticate with an OIDC Identity Provider such as Azure Entra, Google, OKTA, etc.

Option	Description
Grant Type	The OAuth grant type to use. Supported options are: Authorization Code Client Credentials
Authorisation Endpoint	The authorization endpoint of the identity provider.
Token Endpoint	The token endpoint of the identity provider.
Client ID	Client ID of the client registered in the identity provider.
Client Secret	Secret for the client registered in the identity provider.
Scopes	Space delimited list of scopes to request from the identity provider. For example: `openid offline_access`
Redirect URI	Redirect URI that the identity provider should call back to from the authorization endpoint after the user completes the sign-in process. This must be formatted as `<ewa-base-address>/api/integrations/oAuthCallback`. For example: `https://ewaserver.local/api/integrations/oAuthCallback`

Windows Authentication

Use NTLM/Kerberos authentication with OTCM.

Option	Description
Username	The username used to log in to OTCM.
Password	The password for the specified user.