SSL certificates used for ArcMC management of Smart Connectors
I am looking for some further details and explanation on how the SSL certificate is generated on the connector to be used for the ArcMC management.
I have experienced differences in the CN used within the certificate for different SmartConnectors on the same software Connector server. By default, the certificate does not contain the correct hostname of the Connector Server and uses the IP address allocated to one of the Connector server interfaces.
I can generate a new SSL certificate for a specific SmartConnector and in most cases I can enforce this SSL certificate to be used. But again, I have also encountered an issue where even though I have produced an SSL certificate with the required CN. I see that when the agent is restarted a new SSL certificate is being generated and this is being presented to ArcMC. Again this is using an IP address rather than the required FQDN within the CN field of the SSL certificate.
Is there any way of ensuring the auto-generation of SSL certificate uses an FQDN?