Leaderboard

Hi Everyone, Happy to report back here that we now have Pwned integration in our software, in our standard Passwordstate Vault and also in the Password Reset Portal module. After upgrading to 8388 or higher, you will see this option under Bad Passwords: Then, as long as Bad Passwords is enabled on the Password List, when a user goes to add or update an existing password, it will perform a Pwned check and deny them setting the password if it has a match to the online Pwned API. Thanks for the suggestions! Support.

Thanks, and I can see the issue now - I just tested this also: You have your Invoke-RestMethod inside the json object - although you probably have moved this out by now And the GenericField1 and Description fields do not have a double quote before the single quote for your PowerShell variables i.e. should be "GenericField1":"'+$ServerName+'", instead of "GenericField1":'+$ServerName+'", I know it's hard to see in this forum, but cut and paste the text above and you will see what I mean. Regards Click Studios

Hi Michael, This issue is a timeout with your SQL Server, and in the .NET Framework the default is set to 30 seconds for database connections. We're going to make a change in the next release as we've had a few customers run into this issue recently, as we've developed a more efficient script which should hopefully help with this. For now, if you can contact us via our support page on our web site (https://www.clickstudios.com.au/support.aspx) I can provide the SQL script to you now so you can run this manually in SQL Server Management Studio. Regards Click Studios

If you need to import all of your data from KeePass into Passwordstate, this is the preferred process due to the below Powershell script keeping the correct format of your KeePass database. We'd like to thank one of our customers Fabian Näf from Switzerland for writing this script for us. He did a great job and it's helped out many of our customers. Process Start: In Passwordstate, identify and note down your System Wide API key from Administration-> System Settings -> API and you will find it under “Anonymous API Settings & Key” Create a Password List Template under the Passwords Menu -> Password List Templates. On this template please set the following options and then save the template: Disable the option to prevent the saving of password records if they are found to be a “Bad Password” (screenshot 1 below) Uncheck the option so the Password field is not required, and enable the URL field (screenshot 2 below) Identify and note down the TemplateID by toggling the column visibility (screenshot 3 below) In KeePass, open your database and export the contents to a XML file. This can be executed from File -> Export -> KeePass XML (2.x) Download the script from: https://www.clickstudios.com.au/downloads/import-keepass-xml.zip Extract this zip file and open with Powershell ISE or the straight Powershell shell, if you prefer You will be prompted to answer 5 pieces of information: The username of your Passwordstate Security Administrator Your Passwordstate URL Your System Wide API key Your PasswordList Template ID It will ask you to browse to your Exported XML file That’s it, the script will now run through and automatically read all of the information out of the XML file, and import it into Passwordstate. From here, there are a few other things you might want to consider doing after the script has run successfully: You may want to rearrange your folder structure. Ie possibly you might want to create some new folders for each of your teams, and then drag and drop existing Password Lists/Folders inside of them Once you are happy with your Folder structure, you should start applying permissions to either Password Lists or Folders using the following video as a guide: https://www.youtube.com/watch?v=QBJE_xD185U Best practices are to use Security Groups to apply permissions, instead of individual users, if possible Screenshot 1: Screenshot 2: Screenshot 3: Regards, Support

Okay, the restore of the VM snapshot would have caused this - it looks like your VM Snapshot was old, back when you were using an older build of Passwordstate. Basically your files and database are now out of sync. To fix this, can you please follow section '5. Manual Upgrade Instructions' in the following document - https://www.clickstudios.com.au/downloads/version8/Upgrade_Instructions.pdf Regards Click Studios

Hi Yuko, As mentioned in our email, we can assist with this issue as long as your company is willing to purchase maintenance with their software, If this is not a possibility, and we certainly understand if it's not, then hopefully someone from the community can assist you. Regards Click Studios

Hi, I would like to place this Feature Request here because I found nothing about it in the manuals. A member of a team here in my company using Passwordstate V8.3 (one of latest builds) was asking me - When are the accounts in the Recycle Bin deleted permanently? So I went to the System Settings Tab and tried to find out any option to set here but I found nothing about it. It would be nice to get such a feature to enable the auto delete for Recycle Bin's in order to delete accounts older (with regards to the deletion date) than e.g. 90 days. In addition to that it would be nice if a deletion date could be displayed in the "Recycle Bin view". Thanks Best Regards Philipp

Hello Markeldo, We do plan on looking into this as an option at some stage, as soon as we can allocate some time to it. This may be quite a bit of work, as we need to consider everywhere Bad Passwords are used i.e. UI, API, Windows Service. We'd also need this to be an option, for customers who do not want to allow Passwordstate to communicate on the Internet. Regards Click Studios

I requested this for 7.x and i was told that it was to late into the implementation for it, but we provide passwordstate as a service, were our customers log in with a domain account on our domain. however they do not know the net bios and there user names. I would like to be able to select ldap to use userprincipalname instead, since we set users userprincipalname to there emails, or another ldap value if needed. Mainly, i would like to be able to log in useing my email instead of domain/user.