Jump to content

Recommended Posts

With recent updates to Chrome in the first half of 2017, the Chrome browser could potentially treat your certificate as not secure.  Looking at the Security Overview in the Developer Tools, it would not complain about a Subject Alternative Name missing on the Certificate:

 

2017-05-17_10-25-32.png

 

Generating a new certificate through IIS does not fix the issue, as it does not yet include the functionality to specify a Subject Alternative Name.  Below are two possible work arounds you can use, depending on what infrastructure you have in your environment:

 

1. If you are using the standard Self Signed Certificate that comes installed with Passwordstate, this forum post outlines the steps required to generate a new certificate using Powershell:

https://www.clickstudios.com.au/community/index.php?/topic/1948-create-new-self-signed-certificate-powershell/

 

2. Or, If you have a Certificate Store set up in Active Directory, this forum post describes how to generate a new certificate from your store with the correct properties:

https://www.clickstudios.com.au/community/index.php?/topic/1952-generate-a-new-certificate-from-active-directory-certificate-authority/

 

 

If you have any issues with either of these processes, please contact click studios on support@clickstudios.com.au

 

Regards,

 

Support

Click Studios

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×