Version 9.5.0
Changes to Judiciary Onboarding
Release 9.5 brings significant enhancements to the onboarding experience for Judicial users. Presently, during onboarding, Judicial users are asked to check their inbox for an activation email, follow a link, and create a password—a step rendered obsolete since they are now expected to exclusively use single sign-on and federated logins through ejudiciary.net when accessing CFT applications.
With this update, we're streamlining the onboarding journey by eliminating the redundant activation email and password creation step. The remaining onboarding process remains unchanged.
All the highlights of the Release are below. For more detailed technical change log, see 9.5 Technical Change Log.
New Features
None
Deprecated / Removed Features
- Bulk User Management API is discontinued
- Batch Status API is discontinued
Functional Improvements
- Remove activation emails for JOH onboarding
- Automatic detection of ID conflicts during the SSO journey
- Validation of stale user data on reinstation
- Hardened validation on user registration
Fixes
- Intermittent "412 Precondition Failed" in idam-access-config (when updating service accounts)
- Handle invalid activation tokens in InvitationByPin service
Security Changes
None
Operational Improvements
- Upgrade Spring Boot and other libraries