--- title: Changed functionality description: Incompatible changes in PingIDM 7.5.x that may affect existing deployments, scripts, or clients when upgrading component: pingidm version: 7.5 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 keywords: ["Deployment", "Identities", "Compatibility", "Security", "JSON"] superseded_by: https://docs.pingidentity.com/pingidm/8.1/release-notes/changed-functionality.html section_ids: changes_between_idm_7_5_3_and_7_5_4: Changes between IDM 7.5.3 and 7.5.4 changed-trace-denied-754: HTTP TRACE requests denied changed-router-metrics-removed-754: Router metrics removed changes_between_idm_7_5_2_and_7_5_3: Changes between IDM 7.5.2 and 7.5.3 changed-oracle-ucp-template-753: Oracle UCP datasource changes changes_between_idm_7_5_1_and_7_5_2: Changes between IDM 7.5.1 and 7.5.2 default_api_version_for_unversioned_requests: Default API version for unversioned requests changes_between_idm_7_5_0_and_7_5_1: Changes between IDM 7.5.0 and 7.5.1 changed-parameter-authorization-751: _api parameter requires authorization changed-array-comparison-751: Array comparison changes_between_idm_7_4_x_and_7_5_0: Changes between IDM 7.4.x and 7.5.0 changed-fx-flowable-upgrade-680-75: Workflow engine upgrade array_schema_fields_default_to_item_type_string: Array schema fields default to item type string populatedefaults_flag_removed_from_secrets_configuration: populateDefaults flag removed from secrets configuration java_17_required: Java 17 required legacy_hashing_algorithms_removed_from_the_admin_ui: Legacy hashing algorithms removed from the Admin UI secret_store_class_renamed: Secret store class renamed --- # Changed functionality When you update to IDM 7.5.4 from the last major version, the following changes may impact existing deployments. Adjust existing scripts, files, clients, and so on, as necessary. If you are upgrading from an older release, review the changed functionality from all releases after your current version of IDM: * [Incompatible changes (7.4.x)](https://docs.pingidentity.com/pingidm/7.4/release-notes/changed-functionality.html) * [Incompatible changes (7.3.x)](https://docs.pingidentity.com/pingidm/7.3/release-notes/changed-functionality.html) * [Incompatible changes (7.2.x)](https://docs.pingidentity.com/pingidm/7.2/release-notes/changed-functionality.html) * [Incompatible changes (7.1.x)](https://docs.pingidentity.com/archive/#idm) \* * [Incompatible changes (7.0.x)](https://docs.pingidentity.com/archive/#idm) \* \* Download the PDF from the [Documentation Archive](https://docs.pingidentity.com/archive/) under PingIDM / IDM / OpenIDM > IDM X.X Release Notes. ## Changes between IDM 7.5.3 and 7.5.4 ### HTTP TRACE requests denied PingIDM now denies all HTTP TRACE requests. Previously, TRACE requests to paths not handled by IDM returned `200` with the request echoed back. ### Router metrics removed Router metrics have been removed. The IDM router no longer generates: * `router..` [API metrics](../monitoring-guide/api-metrics.html#api-metric-names) * `idm_router___seconds` [Prometheus metrics](../monitoring-guide/prometheus-metrics.html#prometheus-metric-names) Additionally, the `routerMetricsEnabled` property in `conf/metrics.json` is ignored and can be removed. If you have dashboards or other tools that reference these metric names, update them. | | | | - | ------------------------------------------------------------------------------------------ | | | The related `router-filter` and `authorization-check.router-authz` metrics are unaffected. | ## Changes between IDM 7.5.2 and 7.5.3 ### Oracle UCP datasource changes The default Oracle UCP datasource template (`datasource.jdbc-ucp-oracle.json`) has changed: * The JDBC URL format changed from the deprecated SID format (`@host:port:SID`) to the service name format (`@//host:port/service_name`). * The `connectionTimeout` (in milliseconds) property is replaced with `connectionWaitTimeout` (in seconds). The old property was silently ignored by UCP. Update your existing `conf/datasource.jdbc-ucp-oracle.json` file for these changes. Learn more in [Set up Oracle as an IDM repository](../install-guide/repository-oracledb.html#oracle-ucp-datasource). ## Changes between IDM 7.5.1 and 7.5.2 ### 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.5.0 and 7.5.1 ### `_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). ## Changes between IDM 7.4.x and 7.5.0 ### 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 are 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). ### Array schema fields default to item type `string` Schema fields defined as type *array* are required to have an item type defined as of IDM 7.4.0. IDM 7.5.0 defaults the item type to `string` to avoid startup issues if the type is not defined. ### `populateDefaults` flag removed from secrets configuration The sample secrets configuration (`secrets.json`) no longer includes the `populateDefaults` flag. It is safe to remove this from your secrets configuration. ### Java 17 required Running IDM requires Java 17. For more information, refer to [Java requirements](before-you-install.html#prerequisites-java). ### Legacy hashing algorithms removed from the Admin UI MD5 and SHA-1 are supported for legacy reasons, but should not be used in production environments and have been removed from the Admin UI. For more information, refer to [Salted hash algorithms](../security-guide/encoding-attribute-values.html#encoding-salted-hash). ### Secret store class renamed The `org.forgerock.openidm.secrets.config.FileBasedStore` class has been deprecated and replaced by `org.forgerock.openidm.secrets.config.KeyStoreSecretStore`. The old class is currently an alias.