- 18 Jul 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Release Notes - v24.50.02
- Updated on 18 Jul 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Product Name | Cross Identity |
Version Revision | v24.50.02 |
Date | 12.07.2024 |
The release notes v24.50.02 consists of new features introduced in Cross Identity. This new version includes the following items:
New features: 8
What's new in this release:
Sr. No. | New Features | Description |
---|---|---|
CI Features | ||
1. | Consistency in Token Naming | To ensure consistency in token naming across the system, where tokens should be uniformly referred to as "SMS," "Email," and "Soft Token" for clarity and ease of understanding. |
2. | Cached URL Redirection Issue | Identified and updated all direct access URLs within the application to redirect users to the home URL if they attempt to access cached URLs. This improves user experience and prevents confusion caused by encountering error pages. |
3. | Landing Page Redirection for SSO flow | When a user performs Reset Password/ Unlock account during SAML SP flow, after resetting the password/ unlocking the account, SP flow will be completed and the user will land on the target application. |
4. | Locked Account - Account Unlock and Password Reset Integration | If the user account is locked and the user performs a reset password, the user account will be unlocked in the same process. |
5. | Download the identities report from the Identities page | Admin can download the list of identities from the identities page based on the column filters applied. |
6. | Password rotation feature | This feature performs Password Rotation of the PIAM application accounts (both owned and orphan accounts) based on the number of minutes configured on the Application configuration page. |
7. | Forced Sign-On for Thick Client Application | To enhance security and control over application access, ensure that access to thick client applications is only possible through Single Sign-On (SSO) from the Cross Identity (CI) launchpad. |
8. | User should convert to Privileged from Regular immediately after getting access to Privileged Entitlement | When a regular user requests a privileged entitlement - after the approver approves the request, the user immediately converts to a Privileged user. |
Reference Documents
Installation Guide
Sr.No. | Version | Month | Document name |
1. | 24.50.02 | July 2024 |
Admin Guide
Sr.No. | Version | Month | Document name |
1. | 24.50.02 | July 2024 |
User Guide
Sr.No. | Version | Month | Document name |
1. | 24.50.02 | July 2024 |