Search the Community
Showing results for tags 'browser extension'.
Found 4 results
We have noticed what we think may be a bug, or at least not working as we intended. We have a password list that is shared but must provide a reason to view the password. This list contains entries that include URLs. These entries show up as usable by the browser extension when visiting the URL in a browser. The browser extension will allow you to use it but does not prompt for a reason before filling the form fields. An entry shows up in the audit log that it was used but that's all it displays. We tried setting the API usage to mandate a reason when using the API but then you can't use the entry at all and the extension never prompts for a password. Is this by design or a bug in the software? Should (or can) the browser extension prompt for a reason before filling the form fields?
Hi again! Another day, another RFE I was wondering whether it'd be possible for you guys to include the browser extension installers with the base PasswordState installation, similar to what you already to with the Remote Session Launcher. Not all customers will have access to the browsers' respective extension / app stores, so it'd be great if they also came with the base installer. Cheers, Thomas
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.
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.