> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/whats-new-in-openiam/earlier-releases/2025/v4-2-2.md).

# 4.2.2

Released 7 December 2025

OpenIAM version **4.2.2** delivers new functionality, architectural improvements, performance optimizations, and enhancements across the platform, Identity Governance, and Customer Identity (CIAM). The required steps for user upgrading to 4.2.2 version of OpenIAM from earlier versions are provided in this document.

## Platform enhancements

* Added a **descriptive analytics dashboard** providing real-time operational and identity insights.
* Introduced **Prometheus-based monitoring** for system health, performance, and service metrics.
* Completed a **Groovy Manager redesign**, including improved editing, version history, auditing, and advanced search.
* Improved memory and performance efficiency, enabling stable operation in **32GB** environments.
* Reduced backend latency and improved UI responsiveness.
* Migrated core components:
  * Elasticsearch → OpenSearch
  * ETCD → Consul
* Added **platform-level notifications** for maintenance, incidents, and operational updates.
* Continued **React-based UI migration**, covering:
  * WebConsole administration features
  * Self-Service request administration and history
* Enhanced password security with *Have I Been Pwned* integration.
* Improved password validation across all authentication flows.
* Added deployment support for **CJIS** and **STIG** profiles on RHEL.

## Identity Governance enhancements

* Introduced **Segregation of Duties (SoD)** management via the UI, including enforcement during access requests and continuous violation monitoring.
* Major refactor of **Access Certification**, including:
  * Redesigned user interface
  * Performance improvements for large-scale campaigns
  * Event-driven certification support
  * Certification-specific reporting backend
  * Tagging and enhanced search and filtering
* Enhanced **identity verification**, including adaptive flows and Microsoft Teams Bot integration for approvals.

## Customer Identity (CIAM) improvements

* Added configurable and **passwordless authentication** options (FIDO2, OpenIAM Auth App).
* Introduced adaptive password change flows supporting multiple verification factors.
* Enhanced **risk-based authentication** with behavioral analysis, contextual risk scoring, and device intelligence.
* Added **Teams-based delegated management** using group membership.
* Extended identity verification for CIAM onboarding and login flows.
* Improved session management with configurable inactivity and maximum duration limits.
* Added **user profile switching** in self-service without requiring logout.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/whats-new-in-openiam/earlier-releases/2025/v4-2-2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.