This post is part of the Enabling Secure Connection for Web Services series.
The first step in enabling a secure connection for web services, is to bind the certificate to the port which will be used for secure access. As mentioned in the last post, I am using port 48666.
There are two commands which need to be run to bind the certificate; these need to be run via an elevated command prompt.
The first command registers the certificate for the new port; there are three parameters (highlighted) which need to be changed in the command:
- certhas which is the certificate thumbnail
- appid which is an arbitrary GUID; I generated a GUID using the SQL Server NEWID() command