Sitemap

Version 7.0.19

With KeePass Client v6.0.13

Release Date

Aug 10, 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.

New Client

OS X

  • Pleasant Password Server Client is now available on the  Mac App Store

     

New Features

Web Client

  • Role Report
    • See which users have been assigned to which roles, broken down by direct assignment and inheritance through sub-roles.

Improvements

Web Client 

  • Various UI improvements and fixes.
    • Opening an Entry by clicking on the name will now open the Edit dialog if the user has permission to do so.
    • Notes field now expands as you type up to a maximum height.
    • Password Age report loads faster now
  • Timeout Policies for the Web Client and OAuth tokens can be configured in User Policies.
  • The Distinguished Name used for a directory user that has been imported to Password Server can be edited from the Edit User page.
  • SSH and HTTP Proxies can be individually enabled from the Proxy Server page.
  • Users can no longer delete their own permissions on the Root folder.  This prevents a case where no one would have access to the Root.
  • Users with Use Via Proxy permssions for an Entry can now view but not edit the Proxy Settings so that they may know which placeholders and/or unique identifiers to use.

KeePass Client

  • Edit Entry dialog will be read only if the user lacks Edit Entry permssions.

Bug Fixes for New Features

  • Fixed an issue where the Proxy SSH Server key would be written in the logs when the key was changed.
  • Fixed an issue where Custom Fields would be encoded after upgrading from version 6.
  • Fixed an issue where editing Custom Fields would create multiple revision histories.
  • Fixed an issue where attaching a file from the web client would not produce an Audit Event.
  • Fixed an issue that would cause the grid to appear to be empty after editing an Entry from a Tag Folder.
  • Fixed an issue where KeePass could crash if a user tried to edit an Entry without having permissions to View or Edit the Entry Contents.
  • Fixed an issue where KeePass could not edit a recently imported Entry until it had been refreshed.

Known Issues 

  • After importing credentials into KeePass, KeePass must first be refreshed before any edits can be performed.  This issue will be fixed in the next release.
  • 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.

Important

  • 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.