Search the Community
Showing results for tags 'certificate'.
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: 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 stan
Purpose: This process shows you how to generate a new wildcard certificate from your AD Certificate Store, which can be used for your Browser Based Gateway or you can assign it to your Passwordstate URL. Assigning it to your URL will make for a nicer end user experience, as the all browsers will automatically trust the certificate, assuming the user is accessing Passwordstate from a domain joined machine. Disclaimer: These instructions involve granting your web server permissions to a Web Server Certificate template in your AD Store. We encourage you to review and have
Purpose: Updates to the Chrome browser in the first half of 2017 has generated security warnings, if using the Self Signed certificate supplied with your original install of Passwordstate. This process generates and binds a new Self-Signed certificate that overcomes these new security warnings. Prerequisites: - Windows 8.1 or higher, Server 2012 or higher - Powershell 4.0 must be installed on your web server, preferably Powershell 5.0. To check which version you are running, open Powershell and type in $host. If you need to upgrade Powershell, you c