With KeePass Client v7.1.13
Sept 18, 2015
These Release Notes detail the differences between this release and the last version of any type (7.1.11).
- KeePass can no longer import Entries when it is in Offline Mode.
- If a user does not have Offline Access, no Entry information is synced with KeePass when going Offline. (Previously only the password was not synced)
- More fields including, Tags, Custom Fields, Attached Files and Proxy Settings now appear in the History of an Entry.
- Proxy Settings are now restored when Restoring an Entry from History.
- The location of Entry will no longer change when Restoring an Entry from History. It will remain in its current Folder even if it restored from a revision in which it was is in different one.
- Web Client now ignores case in Tag names.
- Fixed an issue with the recent version 6 to version 7 upgrade optimizations and Postgres databases.
- Fixed an issue where the Authentication Type field on the Directory Edit Page would always load as 'Basic' and saving this page would save this potentially wrong value.
- Fixed an issue where users with Offline caches could not open them if KeePass could not reach Password Server.
- Fixed an issue where KeePass could not be untrayed when 2-Factor Authentication was enabled.
- Fixed an issue that would cause Notifications to sometimes fail to send.
- The KeePass Client's workspace cannot be locked when using Two Faction Authentication. (Fixed in KeePass Client 7.1.15+)
- 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.
- 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.