--- title: Deprecation description: The following features are deprecated and likely to be discontinued in a future release. component: pingidm version: 7.4 page_id: pingidm:release-notes:deprecated-functionality canonical_url: https://docs.pingidentity.com/pingidm/8.1/release-notes/deprecated-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", "Query", "Social Authentication"] superseded_by: https://docs.pingidentity.com/pingidm/8.1/release-notes/deprecated-functionality.html section_ids: deprecated-standalone-prog-profile: Progressive profile deprecated-standalone-socialid-auth: Social authentication deprecated-IWA-auth: Integrated Windows Authentication (IWA) deprecated-access.js: Access configuration in access.js deprecated-scheduler-action: Actions on scheduler endpoint deprecated-health-endpoints: Health endpoints deprecated-conditional-queries: Conditional query filters deprecated-self-service-stages: Self-Service stages deprecated-oauthReturn-endpoint: oauthReturn endpoint deprecated-timezone-schedules: timeZone in schedules deprecated-hash-algorithms: MD5 and SHA-1 hash algorithms deprecated-java-date: JAVA_TYPE_DATE attribute type deprecated-action-patch: POST request with ?_action=patch deprecated-minlength-patch: minLength property deprecated-top-level-read-on-config: Read requests at top of /config deprecated-array-of-types: Defining object schema type attribute in an array when it is a single type --- # Deprecation The following features are deprecated and likely to be discontinued in a future release. ## Progressive profile [Progressive profile data collection](../self-service-reference/progressive-profile.html) is deprecated and will be removed in a future release of IDM. This functionality is already supported by AM in a platform deployment. For more information, refer to [Progressive profile](https://backstage.forgerock.com/docs/platform/7.2/platform-self-service/progressive-profile.html) in the ForgeRock Identity Platform documentation. ## Social authentication Social authentication is deprecated and will be removed in a future release of IDM. The feature will be a function of AM. Once a user has logged in through AM (using a social provider or some other way), they can obtain an access token with that session and use the access token to interact with IDM through the [rsFilter configuration](../auth-guide/rsfilter-auth.html). Additionally, Microsoft has deprecated the "Sign In with LinkedIn" functionality as of August 1, 2023. Refer to [Sign In with LinkedIn](https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin). ## Integrated Windows Authentication (IWA) IWA is deprecated and will be removed in a future release of IDM. This feature will be a function of AM. ## Access configuration in access.js In previous releases, access rules were configured in the `access.js` script. This script has been replaced by an `access.json` configuration file, that performs the same function. Existing deployments that use customized `access.js` files are still supported for backward compatibility. However, support for access rules defined in `access.js` is deprecated, and will be removed in a future release. You should move these access rules to a `conf/access.json` file. For more information, refer to [Authorization and roles](../auth-guide/authorization-and-roles.html). ## Actions on scheduler endpoint The `action` parameter on the `scheduler` endpoint was deprecated in Version 1 of the endpoint and is not supported in Version 2. To validate a cron expression, use the `validateQuartzCronExpression` action on the `scheduler/job` endpoint, as described in [Validate Cron Trigger Expressions](../schedules-guide/configure-schedules.html#validating-schedule-syntax). ## Health endpoints The `health` endpoints, used to monitor system activity have been deprecated in this release, as their functionality was not considered to be of much use. The information available on `health/recon` was node-specific. Instead, you can retrieve cluster-wide reconciliation details with a GET on the `recon` endpoint. The information available on the `health/os` and `health/memory` endpoints can be retrieved by inspecting the [JVM metrics](../monitoring-guide/api-metrics.html#api-jvm-metric-names). ## Conditional query filters The syntax of conditional query filters and scripts within notification filters has changed in this release. In previous IDM releases, request properties such as `content` in create and update requests or `patchOperations` in patch requests were referenced directly. For example, a previous configuration might have used the following query filter: ```json "condition" : "content/manager pr" ``` In IDM 7 and later, query filters and scripts should reference the `request` object to obtain any request properties. Sample query filters have been changed accordingly. The previous example would be changed to the following: ```json "condition" : "request/content/manager pr", ``` This syntax is more verbose, but it lets script implementations use request visitors logic based on the request type, and is more consistent with generic router filters. The old request syntax will still work in IDM 7.0, but is considered deprecated. Support for the old syntax will be removed in a future release. Note that this change is limited to notification filters. Filters such as those used with scripted endpoints have never supported direct access to request properties, and are therefore not changing. For more information on notification filters, refer to [Configure notifications](../audit-guide/notification-config.html). ## Self-Service stages Self-Service Stages (described in [Self-service stage reference](../self-service-reference/appendix-stages.html)) are deprecated in this release and support for their use will be removed in a future release. From IDM 7 onwards, this functionality is replaced by [AM Authentication Trees](https://docs.pingidentity.com/pingam/7.4/authentication-guide/about-authentication-trees.html). ## oauthReturn endpoint Support for `oauthReturn` as an endpoint for OAuth2 and OpenID Connect standards has been deprecated for interactions with AM and will be removed in a future release. Support for interactions with social identity providers was [removed in IDM 6.5.0](https://backstage.forgerock.com/docs/idm/6.5/release-notes/#removed-6.5.0). Default versions of relevant configuration files no longer include `oauthReturn` in the `redirectUri` setting. However, for IDM 7.4, these configuration files should still work both with and without `oauthReturn` in the endpoint. ## `timeZone` in schedules In [Configure schedules](../schedules-guide/configure-schedules.html), setting a time zone using the `timeZone` field is deprecated. To specify a time zone for schedules, use the `startTime` and `endTime` fields. ## MD5 and SHA-1 hash algorithms Support for the `MD5` and `SHA-1` hash algorithms is deprecated and will be removed in a future release. You should use more secure algorithms in a production environment. For a list of supported hash algorithms, refer to [Salted Hash Algorithms](../security-guide/encoding-attribute-values.html#encoding-salted-hash). ## `JAVA_TYPE_DATE` attribute type Support for the native attribute type, `JAVA_TYPE_DATE`, is deprecated and will be removed in a future release. This property-level extension is an alias for `string`. Any dates assigned to this extension should be formatted per ISO 8601. ## POST request with `?_action=patch` Support for a POST request with `?_action=patch` is deprecated, when patching a specific resource. You can still use `?_action=patch` when patching by query on a collection. Clients that do not support the regular PATCH verb should use the `X-HTTP-Method-Override` header instead. For example, the following POST request uses the `X-HTTP-Method-Override` header to patch user jdoe's entry: ``` curl \ --header "X-OpenIDM-Username: openidm-admin" \ --header "X-OpenIDM-Password: openidm-admin" \ --header "Accept-API-Version: resource=1.0" \ --header "Content-Type: application/json" \ --request POST \ --header "X-HTTP-Method-Override: PATCH" \ --data '[ { "operation":"replace", "field":"/description", "value":"The new description for Jdoe" } ]' \ "http://localhost:8080/openidm/managed/user/jdoe" ``` ## `minLength` property The managed object property `minLength` is deprecated. When you need to specify a minimum length for a property, use the `minimum-length` policy: ```json { "policyId" : "minimum-length", "params" : { "minLength" : 8 } } ``` ## Read requests at top of `/config` Support for top-level read requests to the `/config` endpoint is deprecated. You can still retrieve a list of config IDs by querying the `/config` endpoint. ## Defining object schema `type` attribute in an array when it is a single type Support for specifying an object's schema `type` attribute in an array when there is only a single type is deprecated and will be removed in a later release. This affects schemas with `type` attribute definitions in the form: ```json { "type" : ["string"] } ``` `type` attribute definitions in this form should be updated to: ```json { "type" : "string" } ``` For additional information, refer to the [JSON schema `type` attribute definition](https://datatracker.ietf.org/doc/html/draft-zyp-json-schema-03#anchor9).