Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


support last won the day on August 15

support had the most liked content!

About support

  • Rank

Contact Methods

  • Google Plus Account

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1054 profile views
  1. That's very odd. All of our SQL Servers are set to a collation of 'SQL_Latin1_General_CP1_CI_AS'. I wouldn't have thought that collation is that much different to the one you selected. We'll set up a new SQL Server tomorrow with your collation, and forms based authentication, and see if we can reproduce the issue. Thanks for working with us on this. Regards Click Studios
  2. Improve Bad Passwords feature

    Thanks Nick I'd expect we'd be able to get reasonable performance as well if we only performed the check on clicking the 'Save' button, but we'd need to think about whether we want to make this change. We've had some customer's who's SQL Server times out trying to insert 10,000 records for our WordDictionary table - I wonder how it will go inserting 300 million records, with 5 GB of data
  3. Improve Bad Passwords feature

    Thanks Nick
  4. Improve Bad Passwords feature

    Hi Nick, Yes, this could be one option, which we did consider. But we're not sure if customers would allow this, as it would allow there users to use bad passwords. Plus if we were performing password resets on AD account, windows machines, databases, etc, they may dislike it even more. We do appreciate the dialog though. Also, those initial links you posted cannot be found - are there any updated ones? Regards Click Studios
  5. Improve Bad Passwords feature

    Hi Guys, With the current design, the database of choice is not really the issue here. We have a Regex partial matching feature for Bad Passwords, which means every keystroke performs a check to see if the password is 'Bad'. Because of this option, we hold the BadPassword data in memory on the Add/Edit screens, for performance reasons. Having 300M records in memory is not an option, as this would be X times 300M records, dependant on how many concurrent users there are logged in. So if we were to explore this, we would probably need to drop the Regex pattern matching, and then make one call to the database when you hit the 'Save' button. This also means we could not show on the screen whether the password is bad or not, only at the time of hitting the Save button. Regards Click Studios
  6. Hello Jack, Sorry you've run into this issue. This may be a bit challenging for us to figure out, as we do only support the English language - we're not smart enough to know more than one language There have been changes in version 8 in terms of the .NET Provider we use for database connectivity, and this is so we can support just having TLS 1.2 protocol enabled - for server hardening. With this change, we have had some date format changes, as this new SQLNCLI11 provider does not allow micro seconds to be passed to the database. So I would expect this is either failing on the DateCreated field in the UserAccounts table, or FormsPassReset if you are using the forms-based authentication version of Passwordstate. Can you please tell us if you are using AD authentication or forms, and I will then compare the two account creation functions and see if there are any differences? Regards Click Studios
  7. Server error when clicking on username

    You're welcome - thanks Jack. Regards Click Studios
  8. Found issues with V8 upgrade

    Hello, You can use the following article as a guide for moving your Passwordstate database to a new server - https://www.clickstudios.com.au/documentation/move-new-database-server.aspx If you also need to move the web site as well, you can follow these instructions - https://www.clickstudios.com.au/documentation/move-new-web-server.aspx We hope this helps. Regards Click Studios
  9. Error on upgrade

    Hi Everyone, This is now fixed as of Build 8065. Regards Click Studios
  10. Server error when clicking on username

    Hi Everyone, This is now fixed as of Build 8065. Regards Click Studios
  11. Hi Everyone, Today we have release build 8065, which includes 1 update and 6 bug fixes. Full changelog can be found here - https://www.clickstudios.com.au/passwordstate-changelog.aspx Regards Click Studios
  12. Improve Bad Passwords feature

    Hi Nick, You're correct in that adding in anywhere near this amount of Bad Passwords would cause massive performance issues every time we needed to check this volume of records. I'm not sure if there's really anything we could do about this, and will probably let customers decide what additional bad passwords they would need to add in themselves. Unless the community has a better suggestion for how we could do this, without impacting on performance. Regards Click Studios
  13. Private password list encryption

    Hello, We use the same 256bit AES Encryption and HMAC Hashing as all other encryption features within our software. You can read about some of the security here - https://www.clickstudios.com.au/about/secure-code-data.aspx There are no issues with using Okta for authentication - our SAML 2 Authentication option is designed to work with this. Regards Click Studios
  14. Server error when clicking on username

    Hi Jack, We're really sorry about this issue, and we're annoyed we never picked it up during the beta testing phase with other customers. It is an issue with our code (not data related), and only affects customers who are using the Forms-Based Authentication version of Passwordstate - Active Directory authentication is not affected at all. We need to release a new build to fix this, which we will have done by the end of the week. If there's anything specific in Preferences you would like changed, let us know as we may be able to help you modify data directly in the database - depending on what you need changed. Regards Click Studios
  15. Error on upgrade

    Hi P_Tone, Thanks for reporting this issue, and we believe you must have your SQL Server configured for case sensitivity - which is not a default setting. We will change this in the next release, so no other customers run into this problem. The second issue would be caused because of the first failure, and you will need to restore a backup of your database, taken just prior to the upgrade attempt. Please let us know if you do not have a backup, as we will need to figure out what database schema's to manually remove. Regards Click Studios