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
  • 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 5 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. GregSmid

    Browser plugin URL matching

    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. 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.
  5. 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.
×