![]() How many certificates will you need? Is it just a couple for your Automic servers, or do you have to manage multiple servers spread across many locations and need to have a centralized view?.Who will be responsible for installing/distributing certificates and configuring TLS/SSL for Automic Automation?.Who is going to be responsible for managing the certificates? Is there a dedicated person/team for the Public Key Infrastructure (PKI) in the company?.Do you need to comply with strict security standards when using Automic Automation, especially in production environments?.Does your company already use certificates signed by a third-party CA, and can they also be used for Automic?.There are several questions that customers need to ask before moving to Automic Automation v21: The Automic Automation TLS/SSL implementation uses public-key certificates in X.509 format and TLS version 1.2 for secure connections between the server and AWI/agents. By signing the certificate with a digital signature, for example, Public Certificate Authority (CA), you can ensure that the certificate is valid and trusted by all clients who trust this CA. Customers have to decide what type of certificates they will use to secure the communications across Automic.Ī public-key certificate contains information like name, hostname/domain name/IP address, validity period, the location that can be used to identify the owner (server), and the public key that the client uses to verify the server. ![]() The next version of Automic Automation mandates TLS/SSL for communications between the engines, Automic Web Interface (AWI), and most agents. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |