> For the complete documentation index, see [llms.txt](https://docs-beta.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-beta.openiam.com/whats-new-in-openiam/earlier-releases/2025/v4-2-1-13.md).

# 4.2.1.13

Released 28 February 2025

Version 4.2.1.13 contains minor upgrades along with security and vulnerability fixes. Below is an overview of the improvements and steps required after upgrading.

## Changes in Groovy scripts

In OpenIAM version 4.2.1.13, the reconciliation feature was refactored to improve load distribution across nodes in a clustered environment and to provide an out-of-the-box report on its results. Consequently, some Groovy scripts were modified:

1. Scripts extending `BaseReconciliationGroupCommand`, such as `iamscripts/recon/CreateIdmGroupCustomCommand/UpdateIdmGroupCustomCommand.groovy`, underwent a signature change.

**Before:**\\

```groovy
Map<String, Attribute> attributes, String activityId, String parentAuditLogId, Map<String, String> dataMap) throws Exception {
```

**After:**\\

```
Map<String, Attribute> attributes, String parentAuditLogId, Map<String, Object> dataMap) throws Exception {
```

2. The signature was also changed for scripts extending `AbstractPopulationScript`.

**Before:**\\

```
public int execute(Map<String, Attribute> line, ProvisionUser pUser) {
```

**After:**\\

```
int execute(Map<String, Attribute> line, ProvisionUser pUser, Map<String, Object> dataMap) {
```

3. The return type was changed for scripts extending `DefaultAuthenticationCustomHandler`.

**Before:**\\

```
String principalConversion(String principal, String managedSysId, String auditLogId) {
```

**After:**\\

```
PrincipalConversionResponse principalConversion(String principal, String managedSysId, String auditLogId) {
```

**PrincipalConversionResponse - Return Type Explanation**

The `PrincipalConversionResponse` class is the return type for methods that handle the conversion of a principal during the authentication process.

When a principal (such as an employee ID) needs to be modified (for example, converted to a user login), this class is used to return the updated principal along with a flag that indicates whether the login entity should be re-evaluated.

**Key Properties:**

1. **Updated Principal (`principal`)**: This represents the updated principal value after conversion (like the user login after mapping).
2. **Login Entity Update Flag (`loginEntityUpdated`)**: This boolean flag indicates whether the login entity should be re-evaluated after the principal conversion.

**Use Case:**\
The `PrincipalConversionResponse` is used in situations where the principal undergoes a transformation during authentication (e.g., converting an employee ID into a user login). It returns an object that not only contains the updated principal but also indicates whether further actions are needed, such as re-evaluating the associated login entity.

{% hint style="danger" %}
**Important note.** In version 4.2.1.13 the Reconciliation History page was removed and its data deleted. Download any reports you need **before** upgrading. From 4.2.1.13 onward, reconciliation produces CSV reports and synchronization results are recorded in the audit log.
{% endhint %}

\## New Groovy scripts

1. A new Groovy script has been introduced for a new batch task - `iamscripts/batch/cancelUARCampaign.groovy`. The details of this new batch task are described in [this document](https://app.gitbook.com/s/0uHWHRgcad6P03ehqgmX/developer-guide/groovy/batch-scripts).
2. A new Groovy script for customizing the `CreateAccessRequest` approver flow is available: `iamscripts/bpm/CustomCreateUserRequestEntitlementsApproverAssociationIdentifier.groovy`.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.