Jump to content

parrishk

Members
  • Content Count

    79
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by parrishk

  1. +1 this would be an excellent feature.
  2. Seeking thoughts on the idea of providing "recovery codes" for a user to use in the event that their MFA option does not work, is lost etc. Typically, a web service will allow the saving of a set of recovery codes (typically 5-10) that can be used once to gain access to their account.
  3. Perfect. It was a little bit of a roundabout way to accomplish it but it works! Just tested and was able to get it working as desired. Thank you for the feedback.
  4. That is close. This setting would work if we could set a policy to require MFA and provide the user the options they can chose. As long as MFA is used that is what my concern is.
  5. Bumping this request again. I had thought this would have been a more popular feature request. Just to summarize... I think it would be beneficial to enforce MFA but leave the user the option to choose which form of second factor they use (Google Auth, Yubikey, etc). Is this an option already (that I have somehow missed) or can it be considered for implementation? Thank you.
  6. Ha! Found the culprit. It looks like there were two "Connect-Src" declared in the Content-Security-Policy header...not sure if this was on your end or my end as I already had some CSP headers in place before Passwordstate began implementing them. Removed the second (CSP will only look at the first declared and ignore any additional) and all is good. Was: default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline' fonts.googleapis.com; img-src 'self'; connect-src 'self'; font-src 'self' fonts.gstatic.com fonts.go
  7. Oh gotchya. Yeah I can see that being a benefit when the password DB gets that large...
  8. Hi @Azkabahn You do have the option to run the report on a per-list basis. Have you tried running it against individual password lists? - Kyle
  9. Hi! That is correct. The report does indeed return passwords that are bad. Thanks,
  10. 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,
  11. 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.
  12. Ulf, what about when running HIBP reports. Does that work? It does for us...just not the button next to the password field.
  13. 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 t
  14. 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.
  15. 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!
  16. 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!
  17. 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!
  18. 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?
  19. 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
  20. 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
  21. 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
  22. Hey! I will do some testing but it was either the "issuer" or the "label" that was missing and some authenticator apps did not show "Passwordstate". Ill see which one it was and report back.
×
×
  • Create New...