Skip to end of banner
Go to start of banner

Release Notes & Updates for Build 7.212.0.0

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

Please note that these release notes are for a future release and are currently in progress. The information contained within may change before the final release. As such, the final release notes will be prepared closer to the official launch date.

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

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, along with their 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.

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.

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 were unable to 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 that users can select any end date for resources as expected. The issue did not affect Business Roles, and the fix now applies to all other resource types.

IN THIS ARTICLE

  • No labels