2 Responses

  1. Hannes
    Hannes at |

    It is the wrong way to get the vIDM certificate from path /usr/local/horizon/conf/ read.
    This only works as long as you use the self-signed certificate from the initial installation process.

    If you install your own certificate in the vIDM, it is written to a certificate store and can no longer be found in the file system. In /usr/local/horizon/conf/ you will still find the old self-signed certificate.
    This error in the documentation was corrected in V2.3.x.
    In the new variant, a request is made to the vIDM web server port (443) using the openssl command, whereby the currently installed certificate is transferred, and the sha256 hash is calculated from this.
    https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.5/administration/GUID-1A78C603-5351-42A8-AE56-F37327E4F8E7.html
    Regards
    Hannes

    Reply
    1. Manjunath M
      Manjunath M at |

      Thanks for the feedback Hannes, I will modify the post based on the NSX-T latest Document for Signed certificate.

      Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.