Related Articles
KB2582 - User Guide: Configuring SSL in Cireson Portal
Preparation
In order to enable SSL in a Cireson application, you must install a valid SSL certificate. Follow these instructions to generate and install your SSL certificate to the server running the Cireson Platform Service. https://blogs.technet.microsoft.com/rmilne/2014/06/17/how-to-request-certificate-without-using-iis-or-exchange/Â
Once you have installed the certificate, you must get the Certificate's Thumbprint.Â
Run the following command in an Elevated PowerShell Command line prompt:
Get-ChildItem -path cert:\LocalMachine\My
This will return a list of certificates with the associated thumbprints. Find the certificate you plan to use for ssl encryption, and copy the thumbprint value for that certificate.Â
Configuration File
To find the config file for your installation, find the installation path
For Service Manager Portal
Default install location is C:\inetpub\CiresonPortal\Platform\.Â
The file is named:Â Platform_cache.config.Â
Open it in a text editor (If using notepad, open notepad as administrator). Ensure you have backed up this file before proceeding.
Step 1:
Locate the following property:
"Urls":["http://*:80/Platform"]
To add the binding for SSL, change the above to:
"Urls":["http://*:80/Platform", "https://*:443/Platform"]
Step 2:
Next locate the SSlCertificateThumbprint property:
"SslCertificateThumbprint":""
Paste the certificate thumbprint from the PowerShell command earlier:
"SslCertificateThumbprint":"977C06XXXXXXXXXXXXXXXXXXEE81A7B"
Note: Spaces or additional characters are invalid in the SslCertificateThumbprint field. See KB2506 for further details.
Save the file, and restart the Platform Cache service.
Additional Troubleshooting
I can't see version numbers for the Cireson Platform Cache in the General Admin Settings on the Cireson Portal, what do I do?
This is most likely caused by using a secure SSL certificate and turning off non-secure website bindings. If the Cireson Portal is installed without an SSL certificate initially and one is applied afterwards, the Platform Cache does not recognise this modification and needs to be updated to use the SSL certificate. This article helps with manually updating the SSL certificate in the Platform.Â
When manually changing the settings in IIS to add a https binding, it's possible to add more information than is required and cause the Platform to get hung up.Â
Administrators should configure their settings as below:
Once all has been configured, restart IIS, the Cachebuilder and the Platform Host, and you should start to see Platform based features once again
