Password Manager Pro Build 9000 Released

Password Manager Pro Release 9.0 (9000) (28^th April 2017) 

New Features, Enhancements, Changes & Fixes

• New User Interface

  From build 9000 onwards, Password Manager Pro will switch to a new user interface (UI) in order to improve user experience. The rich, modern look of the new UI embraces the flat design, and includes enhancements to the speed and usability of the application. Users will be able to navigate between tabs quicker than before and access data without multiple page reloads, thereby equipping admins to get their jobs done faster. This simple and responsive design is optimized across both mobile and web platforms to provide a wholesome experience to the user.

• Important Change in the Design of Criteria-based Dynamic Resource Groups

  From build 9000 onwards, for criteria-based dynamic resource groups, criteria will be applied only on the resources owned by the group owner and on the resources owned by the administrators who have manage permission to the group. Criteria will not be applied on the shared resources. This represents a significant change from the existing design. At present, criteria gets applied on all resources that are owned by the user who is creating the group and on the ones shared with “Manage” permission. Shared resources are being excluded in the new version. Once you move to the latest version, some resources that were part of a criteria-based dynamic group created by you would have been removed from the group due to this change.

  In the new design too, administrators who have access to a dynamic group with “Manage” permission (henceforth known as “Full Access” permission) shall be able to add the resources owned by them to that group. That means, the resources owned by them shall become part of the dynamic group upon satisfying the criteria.

  Note: This change was introduced in PMP 8.0 for those who installed the full version afresh. That means, for customers who have directly installed builds 8000 and above, this behavior remains the same. The above change will be felt only by customers who have been using Password Manager Pro before the 8000 build was released.

• MIB Update for SNMP Trap Settings

  This version includes an update to the MIB (MANAGEENGINE-PMP-MIB), which is integral to SNMP trap configuration in Password Manager Pro. As part of the update, the OIDs used to identify the VarBinds have been revised.

• In v7000 and above, while retrieving passwords, if the user was enforced to provide a reason as configured by the admin, the user was able to retrieve passwords from “Pass Cards” and “All My Passwords” UI by adding just a space in the reason field. This has been fixed.
• In v8600 and above, when Azure Active Directory (AAD) authentication was configured and enabled for users, users from only one specific AAD tenant were able to log in to Password Manager Pro using their AAD credentials while users in other tenants faced login errors. This has been fixed now, by updating the value of the endpoint to which the sign-in requests are sent from Password Manager Pro.
• In v8700 and above, role summary report could not be generated for a role if the respective role name comprised Japanese characters. This has been fixed.
• In v8700 and above, admins using Password Manager Pro’s Premium edition were unable to create API users even though XML-RPC API/SSH CLI access and related operations were allowed in the premium edition. This has been fixed.
• In v8700 and above, if an admin disables the “Personal” tab for users by unchecking the respective option under General Settings, the option itself disappeared from view the next time when the admin accessed General Settings. This has been fixed.
• Earlier, in MSP editions, client organizations that had been marked as favorite by respective users were not displayed at the top of the list as they should be. Instead, the client org that one user had most recently marked as their favorite was globally displayed at the top for all users. This has been fixed.
• Earlier, while importing users from AD/Azure AD, when the admin specifies the users to be imported as comma separated values, the action resulted in error if there was spacing after the commas. This has been fixed.
• Earlier, when users share their resource group with other users, the former faced resource group duplication issues in their UI dashboard whenever the latter added a new resource to that shared resource group. This has been fixed.
• Earlier, while adding an account under a resource, the account could not be saved if the user had earlier enabled a custom password field under “Account Additional Fields” and entered a password containing specific special characters including Greater Than/Less Than ( “<“, “>” ) symbols in that field. This has been fixed.
• Earlier, during manual resource addition operation, the user was able to add two different accounts under the same name but different casing. However, while saving the added accounts, the second account’s user-provided password was automatically replaced with the first account’s password. This has been fixed.
• Customers who upgraded to 8700 from any of the older versions faced an issue with the “Personal” tab, i.e. if they had earlier disabled the Personal tab for users, the provision was automatically enabled for users after the upgrade. This has been fixed.