Locate the file that contains your encrypted public private key pair (ending in .pfx) and copy it to the staging area on your web server.
From your Windows command prompt, type “mmc.exe”
- Upon the opening of Microsoft Management Console, follow these steps
- “Add/Remove Snap-In” (Figure 1)
Select "Computer account", "Next" (Figure 2)
Select “Local computer”, “Finish” (Figure 3)
Click “Ok” (Figure 4)
Expand the “Personal folder” (Figure 5)
- Right-click on the “Certificates” folder
- Select “All Tasks”
- Select “Import”
- Browse to and select the .pfx file
- Select “Place all certificates in the following store”
- Browse to and select “Personal”
“Finish” (Figure 6).
Your personal certificate should now appear in the list of Personal Certificates (Figure 7).
Binding the IIS Endpoint with a .pfx file
Once the .pfx file is installed, you need to use it to bind your endpoint in IIS. Select the ClientPay site in the left side bar and then click on Bindings on the far right of the IIS console (Figure 8 below).
Add a new https binding. You will not be able to change an http binding to https and you will not be able to delete the binding if there is only one so you need to create a new binding and then delete the original one afterward.
Assign the port and leave the “Host name” empty and IP address at “All Unassigned” unless you have a reason to assign a specific address. The port must be either 443,444, 8080, or 32321.
If you are using a Persolvent-generated .pfx, you will see a warning regarding an intermediate certificate (Figure 9). You can click OK and ignore this.
Testing the connection
If you have completed all of the above steps, email firstname.lastname@example.org to let them know you just installed the free certificate and need them to run a connection test. If the test is successful, the process is complete. If there are any errors, our team will work with you to troubleshoot.