Jump to content

Search the Community

Showing results for tags 'chrome'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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
  • 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 9 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. Part of setting up the Remote Session Launcher requires you to configure your browser to add in a custom Passwordstate protocol. This is normally a once off process, however if you clear your cache in the browser this will reset the protocol section. If you are running the latest stable build of Chrome (build 63), then attempting to add this protocol will not save, and hence our remote session launcher will not be able to connect to any machines. This was identified as a Chrome bug in December 2017 and has been patched in the next development version of Chrome. If you
  3. 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?
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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: Brows
  9. 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 in
×
×
  • Create New...