7 Environments (Gateways and Credentials) with Client Credentials Authentication Scheme (OCIM)

Partners who have purchased non-production OPERA Cloud environments can view the information (that is, clientId, clientSecret, EnterpriseID, Scope and gateway URL) required for calling the environment from the Environments page in the Developer Portal. Once partners are ready to call a hotel’s environment, they can add a new environment and obtain the ClientId, ClientSecret, EnterpriseID, Scope, and gateway URL details.

Customers can also view their environment’s clientId, clientSecret, EnterpriseID, Scope, and gateway URL on the Environments page.

Note:

One environment refers to one chain in a single OPERA environment and corresponds to one clientId.

Sandbox Availability

Partners wanting to integrate with customer environments supporting a client credentials-based authentication scheme (OPERA Cloud Identity Management) should refer to the OCIM Sandbox details available on the Partner Developer Portal environments page.

ClientId Format

Starting with OHIP Portal version 25.3.1, newly created clients are in a human-readable format (below) rather than a GUID (e.g., 'a995b6b2-c983-11ee-8c2e-0242ac110002').

Partners: '<cloudAccountName><chain><environment>-<enterprise>-Client'

Customers: '<chain><environment><enterprise>Client' or '<chain><environment><enterprise><clientName>'

This makes it easier to see who made changes when hotels look in audit logs.

The clientName is the same as the clientId to help customers auditing records in OCIM.

Disclaimer: Please note that the Partner Developer Portal provides a set of default sandbox environments, some of which have Streaming enabled. These sandbox environments are shared across multiple partners and developers and may therefore experience cross-tenant activity, such as profile creation, reservation updates, or charge postings.

If Business Events (through Polling or Streaming) are enabled, such shared activity may result in events being generated and queued for consumption by your application. If these interactions are not required, Oracle recommends unsubscribing from Business Events after completing testing and re-enabling them only when needed.