In the earlier post (https://gavinsoorma.com.au/knowledge-base/goldengate-23ai-microservices-deployment-security-part-one/) we discussed how to create the various server, client and Root CA certificates on the source as well as the target.
In this post we will see how we can use the certificates to configure security in source and target deployments and create a secure Distribution Path between the source and target deployment using certificates.
Configure security for deployment Perth (target)
Provide the path for the Server certificate, private key and Root CA certificates.
For the Client Certificate we need to provide path for the Client certificate, private key and Root CA certificates used to sign the Client certificate.
Configure security for deployment Sydney (source)
Provide the path for the Server certificate, private key and Root CA certificates.
For the Client Certificate we need to provide path for the Client certificate, private key and Root CA certificate.
Manage Certificates
In the source deployment (sydney) add the local Root CA certificate as well as the Root CA which was copied from the target deployment (perth).
In addition on the source deployment we also add the Client Certificate which was copied from the target deployment.
On the target deployment, we create a user with the Operator role who is identified by a Certificate.
Provide the path to the Client certificate as well as the Root CA (ext) certificate used to sign this Client certificate.
Create the Distribution Path
Ensure the target host matches the value used while creating the server certificate (perth.localdomain) – and the port in question is the port allocated to the Receiver Service on the target deployment (perth).
Select the Client Certificate (which was copied from the target).
Start the Distribution server.
On the source database an UPDATE transaction is executed.
SQL> update SCOTT.MYOBJECTS set owner=’SYS’ where rownum < 1001;
1000 rows updated.
SQL> commit;
Commit complete.
Verify that the extract has captured the UPDATE transaction and that the Distribution Path has also processed this transaction.
