On-Premises integration using ARCON key vault
- Updated: 2024/12/24
On-Premises integration using ARCON key vault
Procedure to integrate Automation 360 Control Room with ARCON key vault.
Prerequisites
Ensure that you have deployed the following:
- Control Room as software within your customer environment. See Installing Control Room On-Premises.
- Bot Agent within your customer environment where automations run and access customer applications. See Get started with Bot Agent.
Procedure
-
As part of the key vault configuration for On-Premises
deployment , we would be changing some of the values of the installation so to
avoid the conflict we will be stopping the Control Room services:
- Automation Anywhere Control Room Messaging service.
- Automation Anywhere Control Room service.
-
Run the key vault utility (crutils.jar) for the ARCON key
vault configuration:
-
As system administrator of the Control Room, access the
Automation Anywhere Control Room installation directory that was
created during the initial Automation 360 installation.
For example: 'C:\Program Files\Automation Anywhere\Automation360'
-
Download the latest version of the key vault utility
(crutils.jar) from the following
location:
- Open a browser and access the A-People site: A-People Downloads page (Login required).
- Click the link to the latest On-Premises build.
- Click the Installation Setup folder.
- Download the crutils.jar file.
-
Enter the following command to run the key vault utility:
jdk11\bin\java
-Djavax.net.ssl.trustStore="C:\Program Files\Automation
Anywhere\Automation360\pki\trust\store.ks"
-Djavax.net.ssl.trustStorePassword=changeit --module-path lib -jar
crutils.jar -action UPDATE_KEY_VAULT_CONFIGURATION -configPath
"C:\Program Files\Automation
Anywhere\Automation360\config"
- The UPDATE_KEY_VAULT_CONFIGURATION command helps you to edit the ARCON key vault configuration. Example: Enter ARCON to connect to ARCON key vault.
- During the execution of the key vault utility, if there are any trust certificate issues when connecting to the ARCON server, get the server's certificate and import it to Automation 360 trust certificate store by using the command: C:\Program Files\Automation Anywhere\Automation360\pki\trust\store.ks: > jdk11\bin\java -jar certmgr.jar -appDir . -importTrustCert <Full path of the certificate>
- The ARCON server certificate can be in the .cer, .crt, or .pem format.
- The certmgr.jar is part of the installation directory for your use.
-
On the command prompt , enter the following authentication
details:
- Token URL: This is the ARCON host URL to get the token. Example: https://<host>/arconToken
- Device Credential URL: This is the URL to get device credentials. Example: https://<host>/api/ServicePassword/GetTargetDevicePassKey
- Grant Type: Enter password. Only password grant type is supported.
- Authentication username: Name of the ARCON API user, which is used to get an access token with permission to retrieve device credentials.
- Authentication password: Password of the ARCON API user (This value is masked during input and encrypted before it is saved to the file).
A configuration success message is displayed:
-
As system administrator of the Control Room, access the
Automation Anywhere Control Room installation directory that was
created during the initial Automation 360 installation.
-
For reconfirmation, you can manually verify the entries in
keyvault.properties file located at
C:\Program Files\Automation
Anywhere\Automation360\config directory. The directory should
contain the following entries:
Example:
keyvault.type=ARCON_VAULT keyvault.arcon.vault.token.url=https://<host>/arconToken keyvault.arcon.vault.target.device.cred.url=https://<host>/api/ServicePassword/GetTargetDevicePassKey keyvault.arcon.vault.auth.grant.type=password keyvault.arcon.vault.auth.username=<username> keyvault.arcon.vault.auth.user.password=<encrypted password>
-
Restart the following Control Room services:
- Automation Anywhere Control Room Messaging service.
- Automation Anywhere Control Room service.