Release 2024.06.0 - What's New?

Updated on 19 Jun 2024
3 Minutes to read

Print
Share
Dark
Light

Article summary

Did you find this summary helpful?

Thank you for your feedback

Release 2024.06.0 - What's New?

New Features and Notable Enhancements

RapidIdentity Login Page Accessibility Enhancements

Several accessibility enhancements have been made to the IdP login page and login flow that improves the user’s experience when using assistive technologies such as keyboards and screen readers along with minor visual improvements such as increased contrast between elements.

Notable Enhancements include:

More intuitive keyboard navigation and more descriptive prompts during password updates
Improved aria labels on the password visibility toggle buttons
Additional prompts and improved navigation when starting over or selecting help links
Consistency between pages with respect to titles and language settings

New Identity Hub Features and Enhancements

Identity Hub (IDHub), the Next-Generation of Identity Lifecycle Management from Identity Automation, automates and governs the provisioning of digital identities across the enterprise. Designed for technical and non-technical administrative users, IDHub provides an intuitive user interface that simplifies the mapping of identity information between source and target systems with a robust policy engine that provides point-and-click definition of policies to govern the creation, placement, synchronization, update and removal of those identities based on each institution’s unique needs and conditions.
Identity Hub is only available for new RapidIdentity implementations at this time.

Identity Hub Sponsored Account Support

As an extension of Sponsored Account Functionality in RapidIdentity, Identity Hub has added a Sponsored Account Source Adapter. When utilized as part of a Lifecycle Implementation, this Adapter can support importing of CSV files to batch create, update, and deactivate Sponsored Accounts. This feature can be used in conjunction with manually created Sponsored Account, and imported accounts can be modified from within the People Module when necessary.

Creation of Sponsored Accounts via IDHub can utilize policy-based settings, such as Username and Password Creation policies. An additional policy is available for Sponsored Accounts that supports assignment of a Default Manager if an account is imported without one specified. This policy ensures that all imported accounts will be visible in the People Module in RI and can be reassigned to the appropriate manager.

Last but certainly not least, Sponsored Accounts created via IDHub are able to be synced into downstream systems such as Active Directory or Google.

Identity Hub Time Based Provisioning Support

During the Lifecycle Account Management workflow, there are situations that require various actions to occur on a modified timeframe. Time Based Provisioning in Identity Hub provides the functionality to create policies to enforce early activation, late deactivation, renaming actions as necessary for specific users. Let’s take a look at a couple of common use cases, and how this feature can be used to support them.

Teachers need access to their online accounts prior to the first day of school for Pre-planning: An Early Activation Policy can be used here to enable these accounts a specific number of days ahead of their ‘Start Date’. The policy below would enable Teacher Accounts 21 days before their first day of school.
High School Seniors are provided continued access to their accounts after their Graduation Date: A Delayed Deactivation Policy can prolong access to accounts for a specific number of days after a User’s End Date. The policy below is one example of how this could be achieved using a Custom Deactivation Policy.
A staff member has a life event that results in a name change, which needs to be reflected throughout their online accounts: Utilizing a Rename Policy has two benefits for affected Users. First, the policy will automatically generate updated credentials while ensuring the new name has been populated into downstream systems. Second, the policy enforces a delay in the renaming process to alert the user and the Admin to the imminent change. This delay provides an opportunity to revert the change prior to syncing to downstream systems. The following policy shows how to enforce a 5 day waiting period for Renames in IDHub.