Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


parrishk last won the day on November 20 2018

parrishk had the most liked content!

1 Follower

About parrishk

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location
    Florida, USA

Recent Profile Visitors

1103 profile views
  1. Hi! That is correct. The report does indeed return passwords that are bad. Thanks,
  2. Hello, I was not sure how to describe this request in the title... Basically, looking for the feature to require two-factor authentication for all users but give the user the choice on which second factor they use. For example, a user must use AD Authentication and one of the allowed second factor options (Google Auth, Yubikey, etc). Possibly even have the option to support two second factor options. Google Auth and Yubickey (with only one being required at the time of authentication). Does this make sense? Thanks,
  3. Hello! Does the HIBP report on the screen Administration -> Reports return records for the report, is does it return no records? This DOES work. I am able to return reports globally and per password list Are you using any reverse proxies or load balancers We DO use a reverse proxy to access the server from the outside. Thank you.
  4. Ulf, what about when running HIBP reports. Does that work? It does for us...just not the button next to the password field.
  5. Hello, Thank you for your response. Answers to your questions follow: What Build of Passwordstate are you using 8679 What Browser Type are you using Firefox Chrome Brave Internet Explorer Is your Passwordstate-Gateway Windows Service started Yes What sort of certificate did you export to use with the Gateway - is it a trusted certificate, or is it a self-Signed certificate Publicly trusted certificate from GoDaddy With the URL you're using for Passwordstate, is the DNS entry for this from internal DNS, or external? If external, you may need to open access on your firewall to get to the Gateway's default port which is 7273 Internal address is resolvable. Same as primary Passwordstate URL. If you go to the screen Administration -> Remote Session Management and click on the 'Browser Based Gateway Settings' button, if there is a URL specified in the 'Gateway URL' field, please clear this, Save the change, and then test again This is cleared. From your Passwordstate web server, do you have network connectivity to the Host? You can run the following PowerShell command to determine this (change host name and port as appropriate) - test-netconnection hostname.domain.com -port 3389 Test succeeded. Also tested port 7273 with success. Do you have any firewalls enabled on your Passwordstate web server? If so, you may need to allow access on Port 7273 For the time being, firewall is not on. Thank you.
  6. Hello, Build is 8679. So far, this has occured every time since we updated to the version that supports this feature. I can run a report within Passwordstate to check against the API and that works fine. I can also query the API directly (outside of Passwordstate) without issue. Thank you.
  7. Hello, I have walked through each of the troubleshooting steps. Nothing mentioned above has resolved the issue. Certificate is loaded, service is running, port is listening, etc. When attempting to launch a session from multiple different browsers and are displayed with "Please wait while connecting..." indefinitely. What is the next step to troubleshoot? Thank you!
  8. Good morning, It seems that the "Confirm Have I Been Pwned Status" button is not successfully hitting the API (image below). This is allowing weak/compromised passwords to be saved... I do not believe it is an API rate limit issue as I am able to run a report on compromised passwords fine, I just can't use the button on the password page. Any tips on troubleshooting? I have checked the error console but nothing is listed there. Thank you!
  9. parrishk

    Search for Compromised Passwords

    Thanks! This works perfectly.
  10. Hello, Seeking advise on what I am trying to accomplish. Thankful for the recent addition of HIBP and the value it provides moving forward but I am looking at: Running a report to list all accounts that have a "bad" password and is already stored in the DB Searching all accounts by password. For example, if we found out that Password123 is "weak"...how do I search for all accounts with the password "Password123" so they can be addressed? Thanks!
  11. While looking through the HTML source I noticed that each user's "HiddenGoogleSecretKey" is displayed in plain text. Sure the admin already has privileged access to the system and "could" change/reset this value but I think it would be best practice for only the end-user to ever have access to the secret value. Was this intended or is there not a concern for this value being visible to administrators?
  12. parrishk

    HTTP Security Headers

    This is great news! CSP is the most involved of the headers to implement because it "could" prevent parts of the site from functioning/loading. Best option is to set it to "report only" and begin to whitelist the resources as needed. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy-Report-Only. Once these are good you can remove the report only option. Thanks for the update! Kyle
  13. 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.
  14. parrishk

    Title in Google Authenticator

    Jasper, I'm not sure if they will want to add an option to do this...but it could be handy for those that want to customize it. In the meantime, you can create your own barcode via the following format: otpauth://totp/Passwordstate?secret=XXXXXXXXXXXXXXXX&issuer=Password´╗┐state Just grab the secret from your authentication options page and run it through a QR generator. I made a simple PowerShell module to generate custom QR codes... https://github.com/arnydo/qrgenerator/blob/master/invoke-qrgenerator.ps1