---
title: Incompatible changes
description: When you update to IDM 7.3.3 from the last major version, the following changes may impact existing deployments. Adjust existing scripts, files, clients, and so on, as necessary.
component: pingidm
version: 7.3
page_id: pingidm:release-notes:changed-functionality
canonical_url: https://docs.pingidentity.com/pingidm/8.1/release-notes/changed-functionality.html
llms_txt: https://docs.pingidentity.com/pingidm/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
superseded_by: https://docs.pingidentity.com/pingidm/8.1/release-notes/changed-functionality.html
section_ids:
  changes_between_idm_7_3_2_and_7_3_3: Changes between IDM 7.3.2 and 7.3.3
  default_api_version_for_unversioned_requests: Default API version for unversioned requests
  changes_between_idm_7_3_1_and_7_3_2: Changes between IDM 7.3.1 and 7.3.2
  changed-parameter-authorization-73: _api parameter requires authorization
  changed-array-comparison-732: Array comparison
  changed-java-upgrade-732: Java upgrade
  changes_between_idm_7_3_0_and_7_3_1: Changes between IDM 7.3.0 and 7.3.1
  changed-fx-flowable-upgrade-680-73: Workflow engine upgrade
  changes_between_idm_7_2_x_and_7_3_0: Changes between IDM 7.2.x and 7.3.0
  array-order-agnostic-sync: Synchronization JSON array comparison is order-agnostic
  attribute_encryption_on_assignments: Attribute encryption on assignments
---

# Incompatible changes

When you update to IDM 7.3.3 from the last major version, the following changes may impact existing deployments. Adjust existing scripts, files, clients, and so on, as necessary.

If you're upgrading from an older release, review the changed functionality from all releases after your current version of IDM:

* [Incompatible changes (7.2.x)](https://backstage.forgerock.com/docs/idm/7.2/release-notes/changed-functionality.html)

* [Incompatible changes (7.1.x)](https://backstage.forgerock.com/docs/idm/7.1/release-notes/changed-functionality.html)

* [Incompatible changes (7.0.x)](https://backstage.forgerock.com/docs/idm/7/release-notes/changed-functionality.html)

## Changes between IDM 7.3.2 and 7.3.3

### Default API version for unversioned requests

Previously, REST API requests without an `Accept-API-Version` header used the latest available API version for the resource. These requests now default to API version `1.0`. The `consent`, `scheduler/job`, `scheduler/trigger`, and `schema` endpoints default to API version `2.0`.

## Changes between IDM 7.3.1 and 7.3.2

### `_api` parameter requires authorization

Requests passing the `_api` parameter now require authorization. Learn more in [Common REST](../crest/about-crest.html#api-authorize-example).

### Array comparison

Starting with IDM 7.3.0, unordered array comparison became the default behavior. For this release of IDM, ordered array comparison is the default behavior, restoring the default behavior from prior to IDM 7.3.0.

You can now use the `comparison` managed object schema configuration property to choose how JSON array comparisons are made with regard to array order.

Learn more about [managed object schema properties](../objects-guide/appendix-managed-objects.html#managed-object-property-config-properties) and [array comparison](../synchronization-guide/chap-implicit-live-sync.html#array-comparison).

### Java upgrade

You must upgrade to Java 17, which is required by Jetty 12, to run IDM 7.3.2. Learn more in [Embedded Jetty configuration](../install-guide/appendix-jetty.html).

## Changes between IDM 7.3.0 and 7.3.1

### Workflow engine upgrade

The Flowable embedded workflow engine has been upgraded to [version 6.8.0](https://github.com/flowable/flowable-engine/releases/tag/flowable-6.8.0). If you're upgrading from a previous version of IDM and use workflow, this upgrade requires one or more incremental upgrade scripts. For more information, refer to [Upgrade an existing repository](../upgrade-guide/update-repo.html#upgrade-existing-repository).

## Changes between IDM 7.2.x and 7.3.0

### Synchronization JSON array comparison is order-agnostic

JSON array comparison during sync is now *order-agnostic*. This change may negate the need for certain custom scripts within mappings. For example, scripts that were previously required to sort `ldapGroups` values to avoid unnecessary target object updates.

### Attribute encryption on assignments

Assignment attributes are now encrypted if the corresponding connector attribute indicates confidentiality, based on the attribute's `nativeType` (such as `JAVA_TYPE_GUARDEDSTRING` or `JAVA_TYPE_GUARDED_BYTE_ARRAY`). As part of this change, the managed assignment object now includes the following property:

```json
"attributeEncryption" : { }
```

If `attributeEncryption` is not present, the assignment attributes are not encrypted. If the property is present but empty, it will default to IDM's default [encryption cipher](../security-guide/encoding-attribute-values.html). To specify a different cipher, add the `cipher` property. For example:

```json
"attributeEncryption" : {
  "cipher" : "AES/CBC/PKCS5Padding"
}
```

Additionally, `secrets.json` has a new secret: `idm.assignment.attribute.encryption`.