For the setup of HTTPs you need

• a certificate.
• the ID¹⁾ of the application,
• the port to which the web page is bound and
• netsh.

All you need for registration is a free GUID. You can have this generated, for example, via https://www.guidgenerator.com/.

Together with the certificate and the application ID²⁾ of eBiss you bind the certificate to the port on which the web page is configured. If the “Web server event listener” is set to port 7081, then for example

netsh http add sslcert ipport=0.0.0.0:7081 certhash=f9812f7474517e9a9e0880e400dde22264676f3e appid={88B495F4-E5AF-4F39-BD6E-40E9894502DA}

The Service (eBiss.Service.exe) has the ID {88B495F4-E5AF-4F39-BD6E-40E9894502DA}, the 32 Bit Service (eBiss.Service32.exe) has the ID {E4417B73-1F08-4C18-B740-976230EA7E5C}.

The registered certificates can be displayed by :

netsh http show sslcert

Check and note IPPORT and APPID:

netsh http show sslcert

Delivers e.g:

    IP:Port : 0.0.0.0:8443 <- IPPORT
    Certificate hash : 26fe0d63b21e29a53470e2d6657c031f893a0e18 <- ALTER CERT FINGERPRINT
    Application ID : {0f2a6365-7088-45en-be49-440c36b18ffc} <- APPID 
    Certificate Store Name : (zero)
    ...

Delete the previous certificate on the stored IPPORT:

netsh http delete sslcert ipport=0.0.0.0:8443

Install the certificate with a new fingerprint:

netsh http add sslcert ipport=0.0.0.0:8443 certhash=45caceba6f456c1dacbe278703bd2a70ed003ea6 appid={0f2a6365-7088-45de-be49-440c36b18ffc}

The Web Server Event Listener is used to configure whether the logon takes place via user and password or via the Windows Domain Login.

See also:

• https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/how-to-configure-a-port-with-an-ssl-certificate ] How to: Configure a Port with an SSL Certificate
• https://docs.microsoft.com/de-de/archive/blogs/james_osbornes_blog/selfhosting-a-wcf-service-over-https ]Selfhosting a WCF service over Https