Your browser does not allow storing cookies. We recommend enabling them.


Using Custom Certificate for Administration Interface

By default, Tectia Manager uses a self-signed certificate created during the initial configuration (see Initial Configuration for Management Server) to secure the administration interface. It is also possible to use a custom certificate, for example, one issued by your corporate certification authority (CA) or a third-party CA.

The default key and self-signed certificate can be replaced by putting the custom certificate as a PKCS#12-format file called mgmt-www-gui-custom.p12 in the /var/opt/ssh-mgmt/server configuration directory.

If the mgmt-www-gui-custom.p12 file is found, it is preferred over the self-signed certificate.




What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.

    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH

    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now