Download the Connector you are interested in from Oracle Identity Manager Connector Downloads.
Copy the connector zip file to a staging directory on the master node e.g. <workdir>/stage
and unzip it:
$ cp $HOME/Downloads/<connector>.zip <workdir>/<stage>/
$ cd <workdir>/<stage>
$ unzip <connector>.zip
For example:
$ cp $HOME/Downloads/Exchange-12.2.1.3.0.zip /scratch/OIGK8S/stage/
$ cd /scratch/OIGK8S/stage/
$ unzip exchange-12.2.1.3.0.zip
On the master node run the following command to create a ConnectorDefaultDirectory
:
$ kubectl exec -ti governancedomain-oim-server1 -n <domain_namespace> -- mkdir -p /u01/oracle/user_projects/domains/ConnectorDefaultDirectory
For example:
$ kubectl exec -ti governancedomain-oim-server1 -n oigns -- mkdir -p /u01/oracle/user_projects/domains/ConnectorDefaultDirectory
Note: This will create a directory in the persistent volume e:g /scratch/OIGK8S/governancedomainpv/ConnectorDefaultDirectory
,
There are two options to copy OIG Connectors to your Kubernetes cluster:
kubectl cp
command to copy the connector to the Persistent VolumeIt is recommended to use option a), however there may be cases, for example when using a Managed Service such as Oracle Kubernetes Engine on Oracle Cloud Infrastructure, where it may not be feasible to directly mount the domain directory. In such cases option b) should be used.
Copy the connector zip file to the persistent volume. For example:
$ cp -R <path_to>/<connector> <workdir>/governancedomainpv/ConnectorDefaultDirectory/
For example:
$ cp -R /scratch/OIGK8S/stage/Exchange-12.2.1.3.0 /scratch/OIGK8S/governancedomainpv/ConnectorDefaultDirectory/
kubectl cp
command to copy the connector to the persistent volumeRun the following command to copy over the connector:
$ kubectl -n <domain_namespace> cp <path_to>/<connector> <cluster_name>:/u01/oracle/idm/server/ConnectorDefaultDirectory/
For example:
$ kubectl -n oigns cp /scratch/OIGK8S/stage/Exchange-12.2.1.3.0 governancedomain-oim-server1:/u01/oracle/idm/server/ConnectorDefaultDirectory/
The connectors are installed as they are on a standard on-premises setup, via Application On Boarding or via Connector Installer.
Refer to your Connector specific documentation for instructions.