--- schema_version: "1" id: f172f3d3b8bdd453803360b9113d9d12ed5fbc3d43fc60224c75f11c4505283a title: Client ID Enforcement collection: mulesoft version: current locale: ja-jp portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/policies/client-id-enforcement-release-notes.md canonical_url: https://docs.mulesoft.com/jp/release-notes/policies/client-id-enforcement-release-notes source_site: docs.mulesoft.com content_type: documentation content_hash: f893f670b57decdd5c46f45c3140acbfd8b9d569fa16ef513ee3e502c516589f description: MuleSoft Documentation Site latest: true --- # Client ID Enforcement ## [](#1-3-4)1.3.4 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## [](#1-3-2)1.3.2 **May 26, 2022** ### [](#fixed-issues)Fixed issues - Fix policy schema not allowing additional properties via REST API. ## [](#1-3-1)1.3.1 **May 17, 2022** ### [](#fixed-issues-2)Fixed issues - When using HTTP Basic Authentication Header, policy was expecting a specific value for Client ID Expression. ## [](#1-3-0)1.3.0 **May 17, 2022** ### [](#new-features-and-enhancements)New Features and Enhancements - First Flex compatible Policy. - Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration. ## [](#1-2-4)1.2.4 **August 26, 2021** ### [](#minimum-mule-version)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-3)Fixed issues - An error occurred when generating the response of a multipart SOAP request with invalid credentials. ## [](#1-2-3)1.2.3 **January 06, 2021** ### [](#minimum-mule-version-2)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-2)New Features and Enhancements - Added OAS 3.0 code snippet in the policy YAML file. ## [](#1-2-2)1.2.2 **Apr 30, 2020** ### [](#minimum-mule-version-3)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-3)New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are made to the header manipulation engine. - Several performance improvements made in error handling. ### [](#fixed-issues-4)Fixed issues - After the policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). - An error occurred when handling invalid header values of the Basic Authentication policy. - When requests are made to the protected API endpoint with the Client ID Enforcement policy that does not include the client ID and/or secret, a log entry is now created with the details. However, this logging occurs only when you have specified the Debug level in the log4j settings. ## [](#1-2-1)1.2.1 **Jul 12, 2019** ### [](#minimum-mule-version-4)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-4)New Features and Enhancements - Several performance improvements were introduced in this release. ### [](#known-issues)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-2-0)1.2.0 **Apr 26, 2019** ### [](#minimum-mule-version-5)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-5)New Features and Enhancements - Introduced support for encrypting sensitive information related to the policy. The runtime version must be correctly configured to support encryption. Encryption support was introduced in Mule Runtime v4.2.0. - Several performance improvements were introduced in this release. ### [](#known-issues-2)Known Issues - An error occurs in Mule versions v4.1.1, v4.1.2, 4,1,3 and 4.1.4 when a policy is deployed to applications that have the mule-secure-configuration-property-module plugin configured. To resolve this issue, upgrade the specified plugin in the application to version 1.1.0. ## [](#1-1-3)1.1.3 **Jan 10, 2019** ### [](#minimum-mule-version-6)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-6)New Features and Enhancements - Improved RAML and OAS Snippets. ## [](#1-1-2)1.1.2 **Jun 27, 2018** ### [](#minimum-mule-version-7)Minimum Mule Version **Mule 4.1.0** ### [](#new-features-and-enhancements-7)New Features and Enhancements - Added violationCategory in the YAML configuration file for Feedback Loop. ## [](#1-1-1)1.1.1 **May 11, 2018** ### [](#minimum-mule-version-8)Minimum Mule Version **Mule 4.1.0** ### [](#fixed-issues-5)Fixed Issues - An error occurred when attempting to set Authentication in an existing authentication object. This error is now resolved. ## [](#1-1-0)1.1.0 **Jan 25, 2018** ### [](#minimum-mule-version-9)Minimum Mule Version **4.1.0** ### [](#new-features-and-enhancements-8)New Features and Enhancements - Reduced error-handling verbosity in templates. ### [](#fixed-issues-6)Fixed Issues - An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved. ## [](#1-0-0)1.0.0 **Nov 14, 2017** ### [](#minimum-mule-version-10)Minimum Mule Version **4.0.0** ## [](#see-also)See Also - [Client ID Enforcement Policy](https://docs.mulesoft.com/gateway/latest/policies-included-client-id-enforcement) - [Known Issues](https://help.salesforce.com/s/issues)