With KeePass Client v6.0.14

Release Date

Aug 12, 2015

Warning For "Latest" Versions

Latest versions are intended for:

  • early adopters
  • evaluation of the product based on the latest feature set
  • early access for planning of future deployments or providing Pleasant Solutions with feedback.

Latest versions are not ready for large mission-critical deployments, please use the most recent "Stable" version which has been tested much more thoroughly. Features in these Latest versions typically will make their way to Stable versions between 2 weeks and 3 months later.

Improvements

Web Client 

  • Various UI improvements and fixes.
    • User Display Names are now shown in the Security, Notifications and Comment Requirements dialogs

Known Issues 

  • Old versions of Client apps that do not support the Usage Comment feature will not be able to perform actions that have "require comments" turned on.  Make sure you also have the latest KeePass Client if you wish to use these features.
  • This is a significant release and Password Server may take a long time to start back up (only the first time) after the install completes as your database is upgraded.  Remember to back up your database before beginning the upgrade as interrupting this process could leave the database in an unusable state.

ImportantEdit section

  • Windows XP and Windows Server 2003 are no longer supported in Pleasant KeePass Client Version ≥ 6.0.1 (because of the .NET Framework ≥ 4.5 requirement). Users of those legacy operating systems should use Client Version 5.0.3 and Password Server Version 6.4.13 (the most recent to support Client Version 5.0.3) until they upgrade.
  • Nested AD/LDAP groups cannot be imported in Password Server Version 7.0.1 - 7.3.5.
  • Internet Explorer 8 is no longer supported in Password Server Version ≥ 7.0.1.
  • In Internet Explorer, The Password Server must be viewed with Compatability Mode turned off.  Some IE settings force intranet sites to be viewed in Compatability Mode; if these settings cannot be disabled, accessing the Web Client using its fully qualified domain name can get around these settings.
Tag page
You must login to post a comment.