SSM on-prem default browser certificate regeneration problem

[apartyka]

Hi ALL,

I cannot register a product with SSM on-prem using TLS.

SSM hostname (=ssm.example.com) is different then the default browser certificate's SN (=localhost) so I treat it as a main reason.

How to regenerate the default certificate to match the changed Host Common Name?

The doc says that I need to synchronize local accounts...

Neither synchronisation nor restart helps. No onprem-console useful commands...

API?

Thanks in advance

Adam

[Justin Sprake · Accepted solution]

The Cisco community most closely related to the Smart Satellite On-Prem would actually be:

https://community.cisco.com/t5/network-management/bd-p/5931-discussions-network-management

The HTTPS certificate that the UI presents differs from the mechanism that actually receives HTTPS traffic for the purposes of Smart Licensing. To better understand the nature of your connection failure you can review this via 

https://Satellite-ip-address/Transportgateway

https://community.cisco.com/t5/cisco-software-documents/how-to-register-your-device-using-https-to-satellite-smart/ta-p/3747976

[apartyka]

Justin,

You were right! The URL: 

https://Satellite-ip-address/Transportgateway 

is very useful in diagnosing the certificate issue. I think documentation should separate (and explain) three things: Transportgateway webservice certificate, a Browser certificate (Admin GUI webservice) and a certificate to SSM. Just to know what actions influence which certificates and how to diagnose problems (as you advised for transportgateway).

Thanks for your help!

Adam