Oracle GoldenGate Authentication

The goal of an authenticated identity in Oracle GoldenGate is to establish identity authentication between users, applications, and Oracle GoldenGate Microservices deployments. The authentication design provides the option to either validate users and applications with certificates or user credentials stored as credential aliases (username and password pair).

Authentication is implemented and managed using the following options:

• Using credentials (username, passwords): The credentials information is stored in a credential store, which is used to set up USERIDALIAS while setting up database connections. This is the most common method for authentication.

  See Authenticate Users with Credentials for details.

  WARNING: Credential store is read only. You must never try to modify it directly. This includes copying a credential store from one deployment to another. Use the REST API, AdminClient, or WebUI for creation or modification of Oracle GoldenGate artifacts.

• Using Certificates: If a client is authenticated by a certificate, the server stores the signing CA certificate in a trust store so that the server can validate the identity of the client. This is commonly used when using Distribution Paths.

  See Authenticate Users and Deployments Using Certificates