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.


Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more