Jump to content

Search the Community

Showing results for tags 'chrome'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Essentials
    • Announcements
  • Passwordstate 8.x
    • General Support
    • Feature Requests
    • Feature Requests - Completed
    • Known Issues
    • Installing Passwordstate
    • 3rd Party Hardware/Software Knowledge Forum
  • Knowledge Base
    • General FAQs
    • Password Resets
    • Remote Session Launcher
    • Mobile Client
    • Passwordstate API
    • Browser Extensions
    • Password Reset Portal
  • Passwordstate 7.x
    • General Support
    • Known Issues

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Google Plus Account


Location


Interests


Biography


Location


Interests


Occupation

Found 7 results

  1. Hi, we use chrome and the passwordstate browser extension. Being logged in the extension and opening our Wordpress backend or our teamwork (https://www.teamwork.com/) causes enormous problems. The CPU load increases and the website or even the whole browser doesn´t work. If you logout of the passwordstate browser extension everything works fine. This is pretty annoying because we always have to logout of the extension to use the Wordpress backend or teamwork. Kind regards Achim
  2. Build 8180 on Server 2016. In all my browsers when asked to save a password the password list drop down menu only displays three password lists when there are a couple more that I would think should be displayed. Does anyone know the criteria for a password list to be displayed in that drop down menu, or how I can verify if it is showing the correct lists?
  3. Hi all, I'm wondering how the URL matching for the plugin works. If a password is saved with a URL of http://www.domain.com, should the plugin be smart enough to fill in the login info to http://www.domain.com/login.html? What about https://www.domain.com? Can we use wildcards to help it out? It seems like it'll fill in non-exact matches for some sites, but not others... I haven't been able to find any real patterns yet. Thanks! Greg
  4. 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 this process approved before applying to your production environment. 1. Log into your Active Directory Certificate Authority server as a Domain Administrator 2. Open certtmpl.msc 3. In the Properties of the Web Server template, give your Passwordstate web server Read, Write and Enroll permissions, and click OK. 4. Log into your Passwordstate web server as Domain Administrator, open certlm.msc 5. Expand Personal -> Certificates 6. Right click Certificates -> All Tasks -> Request a New Certificate 7. Click Next 8. Click Next 4. Select the Web Server template, and click "More information is required to enroll for this certificate" 4. Change Full DN to Common Name and type in your domain as a wildcard. Click Add. Change the Directory Name to DNS and also type in your domain as a wildcard. Click Add 6. Under the General tab, enter a Friendly name 7. Under the Private Key tab, select the option to make the certificate exportable 8. Click OK and then click Enroll **NOTE** If you are following this process to generate a certificate to be used with your Browser Based Gateway, please refer to Gateway Install instructions in Section 6: https://www.clickstudios.com.au/downloads/version8/Passwordstate_Remote_Session_Launcher_Gateway_Install_Guide.pdf Otherwise, use these instructions below to use the certificate on your Passwordstate website: 9. Open IIS, and set the new certificate to your HTTPS web binding 10. Now from your desktop, you should be able to browse to your Passwordstate website, and Chrome will now treat it as secure Related Error #1: Certificates with a Signature Hash Algorithm of SHA-1 can also generate security warnings in later versions of Chrome. You may see this error below if your certificate is signed using SHA-1. There are different ways to upgrade your Certificate Store to SHA-256 but one of our customers kindly linked us to this article (Thanks Luis ), which helped him out: https://technet.microsoft.com/en-us/library/dn771627.aspx Related Error #2: When requesting this certificate on your web server, the wizard installs it in the Intermediate Certificate Authorities store, which can cause the browser on the web server not to trust the certificate. You may notice this behavior: To fix this, either install the certificate using Internet Explorer into the Local Machine Trusted Root Certification Authority, or just copy and paste the certificate as per the below two screenshots. You'll need to restart your browser for this to become effective: Copy Certificate from This Location: Into this Location:
  5. 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 can do so via these links: Powershell 4.0 - https://www.microsoft.com/en-au/download/details.aspx?id=40855 Powershell 5.0 - https://www.microsoft.com/en-us/download/details.aspx?id=50395 Step 1: On your Passwordstate web server, download and extract the CreateCertificate.zip file from https://www.clickstudios.com.au/downloads/CreateCertificate.zip to a folder of your choice Step 2: On your Passwordstate web server, open Powershell ISE "as Administrator" and load the CreateCertificate.ps1 file you extracted in Step 1 Step 3: On lines 2 and 3 of the script, change the $PortNumber and $URL variables as appropriate. These values can be found in IIS on your web server. You should now be able to execute the script and then check your Passwordstate website is now functioning correctly. if you have any issues, please email Click Studios on support@clickstudios.com.au
  6. As all websites are created differently, it is difficult for our browser extensions to identify the necessary fields on every webpage required to perform the auto-fill function. For sites where our browser extension cannot detect the form fields automatically, it is possible to manually add the required fields. Working with Chrome is the easiest solution, as it has a free extension that helps look for the information on the web page. Below are instructions on how to use this extension: In Chrome, install an extension called Web Developer: Browse to the login page of the site you are having issues with, and select "Display Form Fields" from the Web Developer extension: You should now see the HTML form names as per screenshot below, and will need to look for the Username and Password fields - These form names will be different for each web site you go to: If you now create a record in Passwordstate with the URL of your website, username and password, you will need to also populate the "Browser Form Fields" tab with the information you found in the step above: You will now need to close your browser (all tabs), and reopen it so the extension can update the information from the Passwordstate web site. If you browse back to your website login page, it should auto-fill the forms for you.
  7. On occasion, we add new features to our browser extensions which also requires an upgrade to Passwordstate. Most recently, we released build 7676 of the Browser Extensions, and Passwordstate. By default, Google and Mozilla pushes down new versions of the extensions to your browser, which forces you to also upgrade your instance of Passwordstate (with Mozilla you can turn automatic updates off if required). If you see a screen similar to the one below, there are one of two things you need to do: 1. Upgrade Passwordstate You can following one of the instructions in our Upgrade Manual to upgrade Passwordstate - https://www.clickstudios.com.au/downloads/version7/Upgrade_Instructions.pdf 2. Recycle PasswordstateApps Application Pool After you have upgraded Passwordstate, and if you still see this Build Mismatch error, you will need to recycle the PasswordstateApps application pool in IIS. Below is a screenshot of how this can be done. Once done, restart your browser, and browse back to your Passwordstate web site to auto-configure your extension again.
×
×
  • Create New...