Release Notes for Build 7.212.0.0

We are pleased to announce the release of EmpowerID Build 7.212.0.0, a comprehensive update with new features, enhancements, and refinements aimed at empowering administrators and enriching the user experience. This release emphasizes the following key areas:

Connectors

• Major upgrade transitions all microservices from .NET 6.0 to .NET 8.0. The update addresses the upcoming end-of-support for .NET 6.0, ensuring continued security and support by leveraging the latest .NET framework enhancements. This upgrade does not affect current functionality or performance but is crucial for maintaining future compatibility and receiving ongoing support.

GCP Connector

• We have added and implemented full and delta inventory features for GCP users. The enhancements include:

  • Full Inventory for Users

  • Delta Inventory for Users

  • Delta Inventory for Users in the Connector

  • Full Inventory for Guest Accounts in the Connector

• We have implemented full and delta inventory features for GCP groups and memberships. The enhancements include:

  • Full Inventory Endpoints for Groups and Memberships

  • Delta Inventory Endpoints for Groups and Members in the Microservice

Zscaler Connector

• The functionality for Reconciliation of SCIM groups with Azure AD groups has been added. This functionality retrieves SCIM groups provisioned in Zscaler, matches them with the Zscaler group IDs and Azure system identifiers stored in Azure Blob, and performs a reconciliation process to ensure both systems are aligned. This enhancement streamlines group management and synchronization across both platforms.

• Inventory of Zscaler Segment Groups is now available. This feature follows the JSON inbox method, where JSON data is retrieved and imported into EID. The stored procedure Custom_ZScalerJSONInbox_ProcessResourceSystem handles the processing of JSON inbox entries for each resource system. The processed data is then stored in the EID segment group tables: ZscalerSegmentGroup and ZscalerSegmentGroupAccessPolicy. The JSON inbox data is stored in ZScalerJSONInbox and zscalerjsondoctype, ensuring seamless integration and synchronization across the system.

• We have introduced the capability to inventory Application Segments from ZScaler using the JSON inbox method. This process retrieves JSON data and imports it into the EID system, where it is processed using the stored procedure Custom_ZScalerJSONInbox_ProcessResourceSystem. The JSON inbox entries are synchronized with the EID components, and the application segments and associated data are stored in the relevant EID tables. This ensures a seamless and automated method for managing application segments.

• The feature to inventory Server Groups from ZScaler using the JSON inbox method allows seamless import of JSON data into the EID system. The stored procedure Custom_ZScalerJSONInbox_ProcessResourceSystem processes the JSON inbox entries for each resource system.

• Managing Access Policies in Zscaler is now available from EmpowerID. This integration allows users to seamlessly define and manage access policies within the Zscaler environment directly from EmpowerID. Users can create, delete, and update access policies using a self-service wizard workflow, simplifying the management process and enhancing user experience.

Azure

• This update introduces the detection, reporting, and recertification of stale Azure applications, streamlining the identification and management of inactive applications. The integration leverages the Azure AD Graph API to retrieve application activity data, now recorded in the LastActivityDate field in the ProtectedApplicationResource table. Applications identified as inactive based on this date are automatically flagged and sent for recertification. This enhancement ensures that stale applications are actively monitored, with any gaps in logging promptly addressed to maintain accurate tracking and reporting for recertification workflows.

• A new permanent workflow, AzureCredentialExpirationNotification, has been implemented to automatically detect and manage expired Azure client secrets and certificates across all Azure tenants within the system. This workflow checks all registered tenants, identifies expired credentials, and executes the following actions for each expired item:

  • Deletes the expired secret or certificate directly in Azure.

  • If the deletion is successful in Azure, remove the corresponding external credential in EmpowerID.

  Additionally, for applications with multiple expired credentials, the workflow sends individual notification emails to app owners and credential owners for each expired item, ensuring prompt awareness and action.

Microservices

• Major upgrade transitions all microservices from .NET 6.0 to .NET 8.0. The update addresses the upcoming end-of-support for .NET 6.0, ensuring continued security and support by leveraging the latest .NET framework enhancements. This upgrade does not affect current functionality or performance but is crucial for maintaining future compatibility and receiving ongoing support.

• To address data privacy concerns, a new SearchToLoad configuration parameter has been implemented for the MyIdentity tabs (All People, Internals, and Externals). This enhancement prevents users from viewing a full, unfiltered list of identities unless a search term is entered. By default, the identity lists will display nothing until a search is performed. This feature ensures compliance with privacy regulations and prevents the potential export of user data by requiring searches for specific identities.

• A new enhancement has been introduced to display the Service Principal Object ID on the overview page of Azure applications in the Resource Admin UI.

• This update introduces the ability to assign application rights to individual users and groups. This enhancement allows for more efficient management of app rights assignments, enabling administrators to streamline permissions across multiple users simultaneously. This feature aims to simplify the user management process and improve operational efficiency.

IAM Shop

• In the IAMShop application window, a new feature has been added to improve the user experience when requesting access to applications. A Select All button has been implemented for multi-select FieldType controls, specifically for the MultiSelectCheckBoxList field type. This enhancement allows users to select all values associated with a FieldType in one action, streamlining the selection process and reducing manual entry time. Additionally, functionality has been added to force users to select at least one value when the EnforceFieldTypeSelection flag is true and the isFieldTypes flag is also true. This will ensure users can add to the cart by meeting the selection criteria. The EnforceFieldTypeSelection flag is available in OnboardAzLocalRight WF advanced settings. Added the ability to manage global field types under Applications, allowing users to view, create, and delete field types. This enhancement provides greater flexibility and control over field type management, similar to the functionality available for app-owned field types. Global Field Types will now be listed in the left-side menu, similar to Claim Mapping policies, making it easier for users to maintain and organize field data. This feature benefits customers by improving the management of field types under applications.

• The IAM shop has implemented an enhancement to enforce a minimum character length of three in the search box on listing screens. This update addresses issues of database timeouts caused by excessive load when search API calls were made with fewer than three characters. With this enhancement, the search functionality will only trigger if at least three characters are entered, improving performance and reducing the likelihood of timeouts.

• A new feature has been introduced to the user interface that allows for configuring parameters to control the visibility of all identities. With this update, users will now be required to input at least three characters in the search bar to view identities, addressing the issue of an empty screen displaying by default. Two configuration parameters have been added to facilitate this functionality:

  SEARCH_TO_LOAD: This parameter determines whether the search functionality will be triggered. It will enforce the minimum character requirement for searches if set to true.

• Resource Admin and IAM Shop have added a new configuration option, making the BusinessRequestName field mandatory or optional.

• A new encrypted media streaming infrastructure has been implemented to enhance the security and efficient streaming of PSM session recordings. This approach ensures that all recordings are encrypted by default to protect data at rest, while specific recordings can be encrypted with unique keys, restricting access unless authorized.

  The new solution employs HTTP Live Streaming (HLS) protocol with AES-128 encryption, dividing videos into smaller segments and generating a manifest file for adaptive streaming. This method improves start times and allows seamless playback by dynamically loading segments based on connection strength, minimizing buffering.

  Encrypted segments prevent unauthorized playback, even if downloaded locally. The infrastructure utilizes a streaming server to serve encrypted segments, and the VideoJS player decrypts these on the fly, ensuring secure, on-demand access to recordings without impacting performance.

Resource Admin

• A new Pre-Approved Members grid has been added to the Groups overview. This feature provides a convenient view of members who have pre-approved access, enhancing visibility and streamlining group management by allowing admins to quickly review and manage pre-approved memberships directly from the Groups overview page.

• A new update introduces menu links to enhance navigation across standard functionalities within the Resource Admin. Access to Access Managers (RBAC Owners), Direct Assigned Locations, and Access Request Policy settings is streamlined and available across resources, including Applications, Groups, Management Roles, and Mailboxes. This addition simplifies the management experience, making it easier for users to access these critical functions from any relevant resource.

• The Resource Admin now provides access to inventoried permissions for Shared Folders. This enhancement allows users to view and manage permissions for Shared Folders directly within the Resource Admin.

• The Application Details interface now includes the ProtectedApplicationResourceUsageTypeFriendlyName property, displayed under the App Authorization Model.

• This update introduces the ability to assign app rights to individual users and groups. This enhancement allows for more efficient management of app rights assignments, enabling administrators to streamline permissions across multiple users simultaneously. This feature aims to simplify the user management process and improve operational efficiency.

• Introduced in this update, the PBAC Definition Assignments section now supports assigning Role Definitions to Business Roles and Locations, Set Groups, and Groups within an application. This enhancement allows users to view, add, or remove assignments seamlessly.

• Introduced the "Assign to Person" feature in the PBAC Assignments -> Role Definition Assignments section. This functionality allows users to assign Role Definitions to eligible individuals within the application, streamlining role management by fetching eligible persons, retrieving their roles, and displaying current assignments. Implemented the "Assign to Management Role" functionality within the PBAC Definitions -> Details -> Assignments. Section. This feature will allow users to assign Role Definitions to management roles within an application, including the ability to view, add, or remove assignments.

PBAC

• A new setting now enables splitting business request items by field type values, broadening the applicability of the approval splitting feature. The setting, configured as a pointer column (AzFieldTypeIDToSplitBy) on the AzLocalRight name, allows the designation of a specific FieldType for splitting requests. When this is set, business requests are split per unique value of the specified field type, while other field type values in the assignment are copied to each split item.

Workflows

• Implemented enhancements for the OnboardMailbox workflow, including adding a popup grid search for the Responsible Party and introducing IsRequired parameters for Responsible Party, Owner, and Deputy fields. The lookup now targets a more flexible configuration, allowing customization for the desired audience. Adjustments were made to use GetSearchAdvanced for Owner selection, enhancing accuracy in the selection process. These updates improve the onboarding experience for mailboxes.

• A fix has been implemented for the DisableMultiplePeopleWF, EnableMultiplePeopleWF, and ResetPassword workflows to address an issue where the advanced search options were not displaying when expanding the search box after selecting No for user selection. This update shows the appropriate attributes, ensuring users can efficiently perform advanced searches within these workflows.

• The latest enhancement in the ManageAzLocalRightWizard workflow introduces the capability to set SplitBusinessRequestApprovalPerFieldTypeValue and ApprovalAzLocalRightID for multiple AzLocalRights selections. The Edit Settings for Right label has been renamed to Edit Local Right Settings, and this option has been added to both single and multi-actions within the wizard. A disclaimer regarding setting overwrites has been implemented, and radio buttons are now used for specific checkboxes to ensure changes are made only upon selection. Additionally, the PBAC approval right is now a dropdown, reflecting changes only when a selection is made. This update also allows owners and deputies to be set for multiple AzLocalRights selections, aligning with existing activities in the ManageAzureAppRoleWizard workflow. Finally, the Assign Responsible Party action for multi-selection has been deprecated.

• The Role Definition Information form for onboarding local roles has a new optional dropdown field for selecting the fulfillment group and aligning it with the setup in the OnboardAzLocalRight workflow. Additionally, the section previously labeled App Right Options has been renamed Advanced Settings to provide a more intuitive interface. This enhancement allows users to assign fulfillment groups to roles during onboarding, improving flexibility in role management.

• The ManageComputerWizard workflow has been updated to include support for configuring RDP (Remote Desktop Protocol) and SSH (Secure Shell) connections for computers. This feature enables users to set up RDP and SSH access options directly within the workflow, along with other configurations such as hostname, Telnet, and VNC access. The updated workflow can be accessed through ITShop → Computers → Workflows → Manage Computer Wizard, providing streamlined setup and enhanced control over computer access configurations.

Security Enhancements and Performance Fixes

• This update introduces a crucial enhancement to the MyIdentity feature, addressing data privacy concerns. Users will no longer be able to view a full, unfiltered list of identities under the All Users, Internal Users, and External Users tabs. Instead, the default view for these tabs will be empty, requiring users to enter a search query before any results are displayed. This change ensures compliance with data privacy regulations, preventing unauthorized access to potentially exportable user information.

• A fix has been implemented to prevent token refresh calls from being made after session expiration. Previously, token refresh requests continued post-session expiration, leading to unnecessary calls.

Resolved Issues & UI Fixes

• A fix was applied to the PBAC App Details page regarding the fulfillment time displayed under process steps. Previously, the fulfillment time incorrectly reflected the same date and time as the request.

• Resolved an issue where users could not set the duration for more than three days while requesting resources (except Business Roles) in the IAM Shop, despite the Restricts Length of Access setting being set to No. This fix ensures users can select any end date for resources as expected.

• A bug fix has been implemented to address a horizontal scroll UI issue that affected the functionality of the Role and Location Mapper and Role Mapper tabs. This issue caused the scrollbar to display extra spacing, disrupting the user experience. Additionally, the sorting of the columns was not functioning on the same page, but this issue has been resolved.

• Resolved a UI overlap issue by fixing the alignment and position of hide/show buttons in the Business and Location. This bug was particularly noticeable when accessing the Role and Location Mapper and clicking the Map selected to new button without any selection, causing text to overlay in the classification section and an unclickable button to appear near the save button.

• A fix has been implemented to address the issue of duplicate shopping cart icons in the Resource Admin and IAM Shop. This problem arose due to a UI issue where the app did not utilize the full available width on larger screens or when zoomed out, leading to the cart drawer opening from the far right and creating the appearance of a second cart icon. The fix ensures that the app content now takes the full width, eliminating the duplication of the cart icon when the cart drawer is opened.

• The issue where Azure role access duration was not displayed in the IAM Shop has been fixed. Now, when an Azure role is requested with time duration, users will see this information in the manage access listing.

• A fix has been applied to address an issue where application rights assigned to group members via ResAdmin do not appear in the IT Shop. When a user assigns the application right Group through PBAC Assignments → App Right Assignments, the assignment correctly displays in ResAdmin. However, it is currently missing from the IT Shop under Applications → Manage Access for the user. The expected behavior is that assigned application rights should be visible to all group members in the IT Shop.

• A bug fix has been implemented in the ConfigureApplicationAuthorizationFieldType Workflow to resolve incorrect configuration behavior for specific field types. The following field types—FreeTextRange, FreeTextSingleValue, SingleSelectAutocomplete, and SingleSelectLookupControl—are now correctly displayed in the UI.

• Resolved an issue where the application name was missing from the cart when assigning role definitions without any field type values. This fix ensures that the application name is consistently displayed in the cart, regardless of the presence of field type values.

• The recent update addresses an issue in the Business Request overview where the fulfillment schedule date was displayed twice. This redundant property has been removed. By streamlining the information presented, users can view a single, accurate fulfillment schedule date, improving their overall experience when managing business requests.

• Resolved an issue where the UserPrincipalName (UPN) was not populated during provisioning through RET. Additionally, a CSS bug affecting the Start Date and End Date fields was identified, where the calendar icon was missing, preventing users from easily selecting dates. The only way to load the calendar was to click at the end of the field. This fix addresses the UPN bug and the CSS issue to ensure proper functionality.

• Resolved an issue where the Requestable setting was not saved for multiple selections in the ManageComputerWizard. This fix addresses a specific case within the recently added Multi IAMShopSettings feature.

• The issue with selecting a tenant when onboarding an Azure application has been resolved. Users can now successfully select a tenant from the available list, ensuring a smooth integration process. This fix enhances usability by restoring the expected functionality in the onboarding workflow for Azure applications.

• A new fix has been implemented to ensure that app right-friendly names are consistently reflected in process steps. This update addresses an issue where changes to the AzLocalRight-friendly name were not reflected in the resource-friendly name, resulting in outdated information in requests. The updated logic will apply to future entries by modifying the trigger to automatically update the resource-friendly name when changes occur in the AzLocalRight. Existing entries will not be corrected, but this will work for any created in the future.