Agent and Service Manager communication in v21

[Purneswara Rao Konda]

Hi Community,

We have a setup of Automic 21.0.5 on SUSE 12 SP5 and running fine with single Agent (TLS enabled). However, we have installed CAPKI and ServiceManager on Agent and able to start and stop agent from AWI but I am wondering while starting Service Manager it didn't create default certificate and key files under bin directory (UCYBSMgr_certificate.pem, UCYBSMgr_key.pem) in Agent server and also CAPKI section was not updated. Is it the expected functionality of ServiceManager in Linux or did we miss any thing on the configuration? Please suggest!

------------------------------
Regards,

Eshwar
------------------------------

[Peter Grundler]

Hi Eshwar,

please check in the ServiceManager logfile if CAPKI was found during start. In case of NO: check if the environment variables are present.

https://community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer/viewthread?GroupId=1435&MessageKey=f60bfa15-0a7e-4185-8628-168100233d71&CommunityKey=2e1b01c9-f310-4635-829f-aead2f6587c4&tab=digestviewer

regards,
Peter

------------------------------
Automic Certified Professional/Expert & Broadcom Knight

For AUTOMIC trainings please check https://www.qskills.de/qs/workshops/automic/
------------------------------

[Eric Lontz]

Make sure you have defined in the CAPKI section of ucybsmgr.ini the key and certificate files as well as cypher such as below:

certificate=C:\Automic\Automation.Platform\ServiceManager\bin\ucybsmgr_certificate.pem
key=C:\Automic\Automation.Platform\ServiceManager\bin\ucybsmgr_key.pem
chain=
cipher=DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256
Also ensure that you have in the same section use_capki=y