Question

IT team changed the cerificates. How to do the rest for communication between control room and bot runner?

  • 12 November 2022
  • 3 replies
  • 14 views

Userlevel 2
Badge +8

SSL cerificates are changed. But now botrunner does not work.

 

I try to follow this

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/deployment-planning/on-prem-install/cloud-config-control-room-https-import-cert.html

 

but installation path says C:\Program Files\Automation Anywhere\Automation360.

but i do not see that path, we have: C:\Program Files\Automation Anywhere\Enterprise

i should navigate to this folder on command window?

 

I wrote this:

 

C:\Program Files\Automation Anywhere\Enterprise>jdk11\bin\java -jar certmgr.jar -appDir "C:\Program Files\Automation Anywhere\Enterprise" -setServerCert "C:\Program Files\Automation Anywhere\Enterprise\Certificate.pfx" -privateKeyPass Wccg2477

 

is privateKeyPass controlroom password?

 

it gave me the error:

Error: Could not read the file as PKCS12 key storage: C:\Program Files\Automation Anywhere\Enterprise\Certificate.pfx

 

thanks


3 replies

Userlevel 4
Badge +8

Hello @Semih Öztürk​  Please follow the article below to import the certificate into the windows certificate trusted root store.

https://apeople.automationanywhere.com/s/article/Install-Botagent-certificate-as-a-One-time-activity

Userlevel 4
Badge +8

@Semih Öztürk​ : if you are still facing an issue then please create a support case

 

How to create a support case :

https://apeople.automationanywhere.com/s/article/How-to-create-a-support-case-in-service-cloud

 

if you don't have access to the above link, email the AA Support team "apeopleopsteam@automationanywhere.com" to get access.

Userlevel 4
Badge +7

@Semih Öztürk​ ,

Actually the privatekey pass is the password when pfx file was created and you will need type it when importing the certificate as steps in your command line.

 

Change the location of the pfx file to another where you dont have some kind of restriction.

 

Alternatively you can verify the certificate using openssl

 

openssl pkcs12 -info -in mycertificate.pfx

 

Regards.

Reply