Jump to content

Search the Community

Showing results for tags 'extension'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


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

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL





Google Plus Account







Found 6 results

  1. Hi, We would like to be able to associate custom password fields with forms fields using browser extension. For example, we have some websites where we must logs using Three fields: - Domain - Username - Password Using browser extension, we can only populate username and password. It would be nice to have in the "browser form fields" tab of a password the ability to associate a other standard fields or custom fields, to form fields and having them automatically filled-in. Thanks.
  2. Hello, We have a issue with the browser extension. Auto-fill does not work on multiple sites but it worked earlier. Are there any settings in Chrome which prevent auto-fill? An example of one of these sites is portal.office.com The Browser Form Fields are correct, but it does not fill. Please help.
  3. I’ve used the new function ”Link Account to Multiple Web Site URLs”. I’ve linked 2 accounts to `localhost`. Now when I use the autofill button on the password fields, I get 2 options, but I don’t which is which. The names of the accounts are the following: (I've removed my personal email from the image) So printing out the title for accounts that are of type “Linked URLs” would solve my problem.
  4. Hi everyone, I'd like to recommend that previous versions of the browser extension be available in the extension stores. As a company with what will be a fairly large user base, we have the need to have a stable platform where dev/test/prod pipelines and proper change management can take some time. That time may exceed the duration from when a new version of the extension is released to when we can update the backend platform. The impact of having the extension automatically update and become non-functional because the main platform has not be updated is problematic. Perhaps maintain something like this: Passwordstate-Latest Passwordstate-Previous Even if you provide just the last released version (i.e. you don't need to support every previous version, just the last one as this will still help encourage keeping the platform up-to-date) in the stores, we can at least provide a method (tell them to install the previous version) to our users to keep them working easily. It's still not a great user experience, but better than having to expedite platform level updates because of a browser plugin. I'd really like to avoid lots of helpdesk tickets because the auto-population stops working. I'd be open to other solutions as well but I figured I'd at least propose something to start with. Happy to expand on the idea if needed. Thanks.
  5. Hello, I tried to see if this issue has already been brought up but did not find anything. It has been brought to my attention, the following scenario: A user browses a website, lets say "https://portal.office.com" where they have a password entry saved in their private password list. We also have a high number of shared passwords that have the same URL. When the user browses "https://portal.office.com" the auditing log shows that the user "retrieved password" for every password we have in the database using that URL. I feel that this process should be revised (assuming it has not been yet as we have yet to update to the latest version). There shouldn't be an audit entry stating that the password was retrieved unless it was actually pulled and used. Maybe pull a list of titles/usernames and audit that but not the actual password unless it is intended to be used by the end user. This fills up the auditing log and could cause for some confusion when a user is showing tons of password pulls when they did not intentionally do so. Has anyone else run into this? Thank you.
  6. As I understand it, the current extension is compatible with Chrome. I also understand that Chrome extensions are, by and large, compatible also with Edge (they just need to be placed in the Windows Store). I'd really really like to see this, because it's now just about the only feature keeping me from using Edge more frequently.
  • Create New...