CENM Identity Manager Helm chart

This Helm chart is to configure, deploy, and run the CENM Identity Manager Service on Kubernetes.

Example usage

The example below shows a command that triggers the Helm chart for the Zone Service :

helm install cenm-idman idman --set prefix=cenm --set acceptLicense=Y

The example below shows a command that specifies the size of the volume dedicated for logs:

helm install cenm-idman idman --set idmanPublicIP=X.X.X.X --set prefix=cenm --set acceptLicense=Y --set volumeSizeIdmanLogs=5Gi

Configuration

Parameter Description Default value
bashDebug Display additional information while running bash scripts (useful while investigating issues) false
dockerImage.name URL to Identity Manager Docker image used by the Identity Manager Service Helm chart acrcenm.azurecr.io/identitymanager/identitymanager
dockerImage.tag Docker image Tag for the Docker image used by the Identity Manager Service Helm chart 1.5
dockerImage.pullPolicy Docker image pull policy for the Docker image used by the Identity Manager Service Helm chart. More info: https://kubernetes.io/docs/concepts/containers/images/#updating-images Always
dockerImageCli.name URL to Identity Manager Docker image used by the CENM Command-Line (CLI) tool Helm chart acrcenm.azurecr.io/cli/cli
dockerImageCli.tag Docker image Tag for the Docker image used by the CENM Command-Line (CLI) tool Helm chart 1.5
dockerImageCli.pullPolicy Docker image pull policy for the Docker image used by the CENM Command-Line (CLI) tool Helm chart. More info: https://kubernetes.io/docs/concepts/containers/images/#updating-images Always
volumeSizeIdmanEtc Volume size for the etc/ directory 1Gi
volumeSizeIdmanLogs Volume size for logs/ directory 10Gi
volumeSizeIdmanH2 Volume size for h2/ directory 10Gi
database.driverClassName Identity Manager database connection details org.h2.Driver
database.jdbcDriver Identity Manager database connection details
database.url Identity Manager database connection details jdbc:h2:file:./h2/identity-manager-persistence;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=10000;WRITE_DELAY=0;AUTO_SERVER_PORT=0
database.user Identity Manager database connection details example-db-user
database.password Identity Manager database connection details example-db-password
database.runMigration Identity Manager database connection details true
acceptLicense Required parameter
cordaJarMx Memory size allocated to the main Identity Manager Service container (in GB) 1
idmanJar.xmx Value for java -Xmx parameter 1G
idmanJar.path The directory where the Identity Manager Service .jar file is stored bin
idmanJar.configPath The directory where the Identity Manager Service configuration is stored etc
sleepTimeAfterError Sleep time (in seconds) after an error occurred 120
authPort Auth Service port 8081
serviceRevocation.port Kubernetes service port to access Identity Manager’s revocation endpoint (targetPort) 5053
logsContainersEnabled Defines whether the container displaying live logs is enabled or disabled true

For additional information on database connection details refer to the official documentation: database documentation .

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.