OpenText Core Performance Engineering Platform
This topic describes the shared administration features for OpenText Performance Engineering products.
Overview
The OpenText Core Performance Engineering Platform is a shared administration area for Performance Engineering products. Use it to manage integration services, create access keys for services that require authentication, and view tenant-level AI usage reports.
Open the platform from Administration > Core Performance Engineering Platform.
Create access keys
Access keys are used to authenticate OpenText Core Performance Engineering services and integrations that use key-based authentication. Each access key consists of a Client ID and Client Secret.
The following services and integrations require an access key.
| Service | Description |
|---|---|
| Agent |
Authentication for agents, OPLGs, and public APIs. For details, see Agents, Prepare an OPLG, and Public API. Note: Username and password authentication is deprecated for all agents, OPLGs, public APIs, and plugins. Existing users can continue to use it until enforcement begins in a future release. |
| Integration |
Authentication for CI pipelines and analytic data integrations. For details, see CI plugins, MCP integration, SiteScope, Git integration, and Time series database streaming. |
| Analysis |
Authentication for OpenText on‑premises products that stream data into OpenText Core Performance Engineering Analysis. For details, see OpenText Core Performance Engineering Analysis. |
| Aviator |
Authentication for OpenText on‑premises products that use Core Performance Engineering Aviator, such as VuGen. For details, see OpenText Core Performance Engineering Aviator. |
To create an access key:
-
Go to Administration > Core Performance Engineering Platform.
-
On the Access keys page, click the Create button
. -
If prompted, select the required service. For details about the available services, see the table above.
-
In the Access key created window, copy the Client ID and Client Secret.
Note: The Client Secret is displayed only once at the time of creation. Store it securely. If it is lost, you must delete and recreate the access key. For details, see Revoke an access key.
Manage access keys
You can view access key details and revoke access keys from the Access keys page.
Access key visibility options
Administrators can view all access keys in the tenant. Use the Show only my keys switch on the Access keys page to control which keys are displayed.
| Switch state | Description |
|---|---|
| Off (default) | Displays all access keys in your tenant, including keys that belong to other users. The Created by column indicates the owner of each key. |
| On | Displays only access keys that belong to your user account. |
Note: This switch setting does not persist across page refreshes. It resets to the default off state when you reload the page.
The following permissions apply to Platform Admins on the Access keys page.
| Action | Permission |
|---|---|
| Create access keys | Can create access keys only for their own account. |
| Revoke access keys |
Can revoke only their own keys. |
When configuring an access key to stream data to OpenText Core Performance Engineering Analysis:
-
Access keys generated from Administration > Core Performance Engineering Platform are used to integrate OpenText Professional Performance Engineering with OpenText Core Performance Engineering Analysis.
-
To integrate OpenText Enterprise Performance Engineering 26.3 and later with OpenText Core Performance Engineering Analysis, a tenant administrator must generate the key in OpenText Core Performance Engineering Analysis from Tenant management > Access keys. For earlier OpenText Enterprise Performance Engineering versions, generate the key in Administration > Core Performance Engineering Platform. For details, see Access keys in the OpenText Core Performance Engineering Analysis Help Center.
-
The same key retention policy applies to all access keys, including keys used for integration with OpenText Core Performance Engineering Analysis. For details, see Automatic access key expiration.
For setup details, see OpenText Core Performance Engineering Analysis.
View access key details
Go to Administration > Core Performance Engineering Platform > Access keys. The grid displays the following information.
| UI element | Details |
|---|---|
| Client ID | The Client ID issued for the access key. |
| Service |
The service associated with the key: Analysis, Aviator, Agent, or Integration. |
| Created by |
Identifies the owner of the access key. Displayed for administrators when Show only my keys is off. |
| Last access | The date and time the access key was last used. |
| Creation time | The date and time the access key was created. |
Revoke an access key
-
Sign in:
-
VuGen users: Sign in to MyAccount and select your Core Performance Engineering Aviator tenant.
-
Core Performance Engineering Analysis users: Sign in to your Core Performance Engineering Aviator tenant.
-
-
Go to Administration > Core Performance Engineering Platform > Access keys.
-
Select the key to revoke.
-
Click the Revoke button
, and confirm.
Automatic access key expiration
For security reasons, access keys expire automatically every 90 days by default.
-
Account administrators can activate, deactivate, and modify the expiration frequency at the account level in MyAccount.
-
When enabled, email notifications are sent to key owners 30 days, 7 days, and 1 day before expiration.
To customize the expiration policy:
-
Sign in to MyAccount and click the Settings button
. -
Select the account you want to modify and open the Security tab. The Custom OAuth expiration policy option is enabled by default with a 90-day expiration period.
-
In the Account configuration area, click the Edit button
, and modify the expiration policy as required:-
Select an expiration frequency between 90 and 360 days in 30-day increments.
-
To deactivate automatic key expiration (not recommended), clear the Custom OAuth expiration policy checkbox. Click Continue to confirm that you are aware of the increased security risks and assume full responsibility for deactivating the feature.
-
-
Click OK to save the changes. All keys of all products associated with the specific account inherit these settings and have the same lifetime.
The OAuth client area in MyAccount displays the client instances created for the logged-in user. Any user with a client instance can manually refresh the key before it expires.
Note: You can keep the same Client ID and refresh only the Client Secret.
Access key guidelines and best practices
The following guidelines and best practices apply when working with access keys:
-
A user can have a maximum of two access keys. To create another key, first revoke an existing key.
-
Access keys are tenant-specific. A separate key is required for each tenant.
-
Rotate access keys periodically, even when automatic expiration is disabled.
-
The recommended lifetime of an access key is 90 days.
-
Do not embed access keys directly in code.
-
Remove unused access keys.
Your organization may have different security requirements and policies. These recommendations are intended as general guidelines.
Caution: Do not share access keys with third parties.
AI Usage report
The AI Usage report provides aggregated visibility into AI query consumption at the tenant level.
Only successfully completed queries are included in usage. Queries stopped automatically by the system or terminated by a system error are not included.
To view the AI Usage report:
-
Sign in to MyAccount and select your Core Performance Engineering Aviator tenant.
-
Go to Administration > Core Performance Engineering Platform > AI Usage.
-
Select the Year and Month.
-
Select My Usage to view your query usage or Total Usage to view total usage for the selected period.
-
Review the usage metrics and breakdown by source tool.
-
To export the report, click Export as CSV.
Exported files include the selected tenant and time range, applied filters, and aggregated totals and distribution views.
Note: Usage data is aggregated for reporting purposes and might not reflect near real-time usage. If you identify inconsistencies, open a service request.

