Jump to content

Fabian Näf

Members
  • Posts

    205
  • Joined

  • Last visited

  • Days Won

    11

Fabian Näf last won the day on June 22 2022

Fabian Näf had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Fabian Näf's Achievements

  1. +1 for OTP I think the whole extension would deserve an upgrade, as it's quite buggy sometimes (at least with Firefox). The bugs have already been reported but never fixed.
  2. Hi buddies, A while a go a created the following feature request for Passwordstate 8. This topic is related to this feature request and to the issue I'm facing explained in the feature request. The main problem I'm facing is, that the Passwordstate extension (mainly used with Firefox) keeps me asking to save credentials whenever there's a random password field somewhere on a website. Mostly it's the field for two factor authentication or when I'm using e.g. a user management with a random password field somewhere on the wesite. When changing to the next webpage the Passwordstate extension will ask me to save this "credentials" ("Add Site to Passwordstate?"). Just that there's a HTML passwod field somewhere on the page seams to trigger this popup. As I've already saved my credentials, I don't want to save any more credentials. The Passwordstate extensions always shows me three options: "Later" -> I'll get the same message again next time "Never" -> This helps, but it also will stop the extension from filling the form for other credentials, not what I'm looking for. "Save" -> Not what I'm looking for, as the credential is just some random data and not a real credential. This time around I try to log this issue as a question in the general support forum, rather then directly coming up with a feature request and a proposed solution. What kind of action do you guys see that I could do to get rid of this annoying popup all the time ("Add Site to Passwordstate?")? Best regards, Fabian
  3. Yes I did. The Health Check Utility stated that everything's fine.
  4. I'm also experience this issue. My upgrade to version 9 was not so smooth. After using the inplace upgrade I got a "SQLite assembly could be loaded" errors in the event viewer and Passworstate was not running. Then I did a manual upgrade by using the upgrade tool (chapter 5 in the manual) with PasswordstateManualUpgrade.exe. I also had to install PowerShell 5 for this step, which could have been the issue with the initial inplace upgrade. => So I also did a manual upgrade and I'm still having this issue.
  5. Hi Stan, Not sure if this helps, but what you can do: You can clone a folder. This is what we do in our company: We have a predefined structure of Folder/Passwordlists as sort of a template and we copy this structure for every customer. Regards, Fabian
  6. I've Passwordstate installed on a dedicated server and accessing Passwordstate from my Laptop and from my VDI client, which both are independent from the server where Passwordstate is installed. All the best, Fabian
  7. Thank you very much, highly appreciated! Best regards, Fabian
  8. Thanks for your fast reply and your explanation. I totaly understand, that you can't forward my laptop, while it's turned off. But why don't you always redirect to the SAML logout URL (HTTP status 302, HTTP Header Location) instead of showing the IIS timeout logout page when my computer turned on again? Best regards, Fabian
  9. Hi Buddies! I'm using Passwordstate mainly from two computers, from my laptop and from my VDI client. The VDI client is always running and the laptop I turn in hibernate mode after working. Regarding the session timeout I'm experiencing different behaviours from the two clients. VDI Client On the VDI client, which is always running, the session timeout is working perfectly and I'm getting logged out from my SAML provider after the timeout limit has been reached. When I login to the VDI client the next day, I see the SAML provider's logut page, which is: https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0 Then I have to do a complete sign in to the SAML provider again to be able to access Passwordstate . Exactly what I want :-) Laptop On my laptop I'm experiencing a different behaviour. When I put my computer into hibernate after work and turn it on the next day, I see the logout page of Passwordstate (in the meantime the session timeout has been reached). After pressing the button to logon again (on the Passwordstate logout page), I'm getting forwarded to the SAML provider's logon page, where I'm still logged in (I never got logged out from the SAML provider). So I'm directly getting forwarded to Passwordstate from the SAML provider and I'm logged in to Passwordstate, without entering any credentials, even though the session timeout would have been reached. As SAML provder I'm using Azure AD and have the following URL configured for logout (default): https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0 On both computers I'm using Firefox as browser. When I use the "Logout" button, logout just works fine, I'm getting logged out from the SAML provider. Summary: When my computer is turned off, the session timeout is reached in the meantime and I turn on my computer again afterwards, I'm not getting logged out from the SAML provider, I'm only getting logged out from Passwordstate. As I'm still logged in to the SAML provider, I can directly access Passwordstate without entering any credentials. Best regards, Fabian
  10. No I have like 10 hosts and 3 folders in the test-environment, where I discovered the issue. The limit is just set as something like a precaution ;-)
  11. I'm running build 8951 and experiencing the issue with Load on Demand enabled and setting "Limit the number of displayed Node" to 1000. All the best, Fabian
  12. @support Thanks for fixing that issue! I just discovered the same problem, when turning on the on demand feature on the hosts tab. Not a major thing, but I thought, this could probably be fixed as well...
×
×
  • Create New...