Oracle Cloud Infrastructure Documentation

Enabling Multiple IDCS Endpoints in Thales HMS

Add more than one IDCS endpoints in the Thales HSM system using API approach.

This API-centric approach offers a programmatic way to manage and configure identity providers, ensuring a scalable and automated process. For more information, see Create Issuer API Documentation.

Prerequisites

Before you begin, understand the following prerequisites:

  1. IDCS Domain Replication: Replicate IDCS Domain in Oracle Cloud Infrastructure (OCI). This replication ensures that the primary and secondary IDCS domains are synchronized, providing redundancy and high availability.
  2. Consistent URLs: Both the primary and secondary IDCS domain URLs need to be configured with the same values in the Thales system. This consistency is vital for seamless operation and ensures that Thales HMS can communicate with the correct IDCS endpoints.

Implementing the API Integration

To add multiple IDCS endpoints, follow the steps outlined in the API documentation:

  1. Endpoint Creation: Use the provided API endpoint to create a new issuer (IDCS endpoint) in the Thales system. This process involves sending a POST request with the necessary configuration details, including the IDCS domain URL.
  2. Authentication Configuration: The API allows for setting up authentication details, such as client ID and secret, to ensure secure communication between Thales HMS and the IDCS domain.
  3. Testing and Verification: After configuring the endpoints, test the integration by initiating API calls and verifying the communication between Thales and the added IDCS domains.