TeamPage 6.2.59 is focused on improvements to external directory service integration, particularly Azure AD. TeamPage now supports retrieving, storing and using profile pictures associated with external users and/or groups and roles. This currently applies only to Microsoft Azure AD configurations, since that is the only external directory service that TeamPage supports which has support for profile picture images. The release also includes several non-security related bug fixes. Please read on for the full list of changes.
• Fixed a URL encoding issue that could prevent some document links from working properly if one of its ancestor folder's names contained certain characters. (Proteus17579)
• Fixed a bug that prevented the "Enable Version Control" and "Check Out" document management operations from being available even if the requesting user should have been able to use them. (Proteus17583)
• Fixed a bug that prevented TeamPage's document management pages from correctly notifying users of certain kings of errors or failures that happened during an attempt to perform certain file management operations. (Proteus17574)
• Fixed a bug that caused literal HTML formatting markup to be displayed in the file history details dialog. (Proteus17581)
General
• Fixed a regression introduced in TeamPage 6.2.57 which could, in some cases, prevent TeamPage from generating certain setup pages. The requesting user would see either an error page, or a partial page with a generic error message embedded in it ("java.lang.NullPointerException: There was an unexpected problem servicing this request.") (Server98995)
• Fixed an issue that prevented TeamPage from gracefully handling the case of two TeamPage user accounts being mapped to the same external user account security principal. TeamPage will now also always scan all user accounts on startup to ensure no users are mapped to the same external user, and if any duplicate is found, one of the accounts will be migrated to a native TeamPage user account security principal to avoid any unexpected issues. This type of collision should be very rare, since this is not normally a condition that TeamPage allows to occur, but if it does happen, it will no longer cause unpredictable behaviors, such as preventing some setup pages from being usable. (Server99105 / Server99106 / Server99121)
Improvements
External Directory Service Integration
• Greatly improved the performance of user searches when using an external directory service such as Microsoft ActiveDirectory or Microsoft Azure AD. This affects all kinds of user lookups as well as email lookups, such as type-ahead completions offered for users in the unified search box, task Assigned to and Notify fields, the email reply and email articles pages' To, Cc and Bcc fields, and everywhere TeamPage offers searches for users. Performance improvements have also been made in the same area for native TeamPage user accounts. Improvements will be most noticeable in environments with a large number of users (e.g., several thousand). (Server99086 / Server99095)
• Greatly improved the performance of the principal details dialog for groups defined in Azure AD which have a large number of members, or for any Azure AD principal (user, group or role) that belong to a large number of groups and/or roles. (Server99085)
• Added optional support for migrating references to externally defined groups when migrating to a new user directory configuration. References to each externally defined group appearing in ACLs or TeamPage's local group definitions can either be replaced by a reference to a group defined in the new directory service, left alone (for later cleanup), or removed. (Server96846)
• Correspondingly, the user directory test dialog now includes the option to test group lookups as well as the existing options to test user lookup and authentication (when applicable and supported). (Server99119)
External Profile Picture Images
TeamPage now supports retrieving, storing and using profile pictures associated with external users and/or groups and roles. This currently applies only to Microsoft Azure AD configurations, since that is the only external directory service that TeamPage supports which has support for profile picture images. (Server99085)
- For TeamPage accounts associated with external user accounts, TeamPage checks for a profile picture image belonging to the external user account. If it finds one, it retrieves it and stores it in the TeamPage user's profile picture collection.
- Approximately once every 24 hours, TeamPage checks whether a new picture is available, and updates the locally stored copy as necessary.
- Profile picture images from external sources can be distinguished by a title tip that appears on hover identifying their source and the last time they were retrieved.
- Administrators can indicate whether TeamPage should support external profile pictures from Azure AD at all, and if they are supported, whether users must opt in or opt out of having TeamPage automatically retrieve them. In the opt-in mode, TeamPage will not retrieve a particular user's profile picture image from Azure AD until the user navigates to their account settings > Personal Info page under Profile Picture and select "yes" for the setting labeled "Allow TeamPage to Retrieve and Retain the Profile Picture from My External Account". In the opt-out mode, TeamPage will automatically attempt to retrieve the profile picture image from Azure AD until and unless the user chooses "yes" for the same setting.
- Users can also manually request that TeamPage retrieve or refresh the local copy of the external profile picture image using the control in the profile picture manager.
For Developers
• TeamPage's html.js SDL tag now correctly handles protocol-relative URLs. (Server99010)
