> 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/2024/v4-2-1-10.md). # 4.2.1.10 Released 15 July 2024 Version 4.2.1.10 contains minor upgrades and security and vulnerability fixes. The sections below provide an overview of the improvements and steps required after upgrading. ## Improvements * Direct reports screen in SelfService had several issues related to performance, sorting and navigation, which were fixed. * Access request (inbox) performance was improved. * The issue with Administration page loading slowly on big data sets (Microsoft SQL database) was addressed. ## New features * New policy for minimum challenge responses questions’ answer length was introduced. * The OTP resend code time is now configurable. * A support for identity center in AWS connector was introduced. * The frequency of OTP tokens that can be sent over SMS and Email was made limited. * A support for proxying Twilio SMS and Voice OTP was added. * Automatic organization hierarchy assignment is now allowed to be disabled. * A new Password history screen is available in SelfService. * Terminating users via SelfService Admin Actions now can trigger a workflow but remain compatible to process requests without invoking the workflow. ## Connectors Two new connectors were introduced to work with OpenIAM - Azure Graph R connector and SAP Fiori connector. ## Additional steps after upgrade 1. An `org.openiam.elasticsearch.model.UserDoc` document in Elasticsearch needs to be reindexed. More on reindexing can be found in the document by the [link](/administration-guide/operations/rebuild-a-search-index.md). 2. The notify method in `iamscripts/prov-helper/CustomConnectorResponseListenerHandler.groovy` needs to be updated. The script can be found after following [this link](https://bitbucket.org/openiam/conf/src/RELEASE-4.2.1.10/iamscripts/prov-helper/CustomConnectorResponseListenerHandler.groovy). 3. Since errors were fixed in OOTB were fixed, we recommend to update `iamscripts/sync/identities/refreshIdentity.groovy`. The updated script can be found [here](https://bitbucket.org/openiam/conf/src/RELEASE-4.2.1.10/iamscripts/sync/identities/refreshIdentity.groovy). 4. In case you are going to use synchronization of Licenses from Azure, note, that three new x files were added, being [iamscripts/sync/group/azure/AzureLicenseSyncAttributes.groovy](https://bitbucket.org/openiam/conf/src/RELEASE-4.2.1.10/iamscripts/sync/group/azure/AzureLicenseSyncAttributes.groovy), [iamscripts/sync/group/azure/AzureLisenceSync.groovy](https://bitbucket.org/openiam/conf/src/RELEASE-4.2.1.10/iamscripts/sync/group/azure/AzureLisenceSync.groovy) and [iamscripts/sync/group/azure/AzureUserLicenseMappingSync.groovy](https://bitbucket.org/openiam/conf/src/RELEASE-4.2.1.10/iamscripts/sync/group/azure/AzureUserLicenseMappingSync.groovy). 5. New files were added for Azure Graph connector provisioning. They can be downloaded by following [this link](https://bitbucket.org/openiam/conf/src/RELEASE-4.2.1.10/iamscripts/provision/azure/). 6. New synchronization scripts for `AzureAuthenticationAssignments` were provided. Follow the links below to find them. * Attributes script: . * Transformation script: . * Validation script: . 7. An improvement in `iamscripts/sync/user/ad/ADPowerShellTransformation.groovy` was introduced to synchronize related accounts. The upgrade script is stored [here](https://bitbucket.org/openiam/conf/src/RELEASE-4.2.1.10/iamscripts/sync/user/ad/ADPowerShellTransformation.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/2024/v4-2-1-10.md?ask=&goal= ``` `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.