--- schema_version: "1" id: e91465c2169e4fbead68c82abe3f8bf7807f3a09ffcb83aa8687651061918b06 title: PingFederate Access Token Enforcement collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/policies/pingfederate-oauth-token-enforcement-policy-release-notes.md canonical_url: https://docs.mulesoft.com/release-notes/policies/pingfederate-oauth-token-enforcement-policy-release-notes source_site: docs.mulesoft.com content_type: documentation content_hash: ce48b7426b9ca00f732e1a4c383d72f502954ae23ee688bca316d833abbbdaae description: MuleSoft Documentation Site latest: true --- --- product: Release Notes version: master keywords: mule, ping federate, oauth 2.0, policy, release notes --- # PingFederate Access Token Enforcement > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## 1.6.1 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## 1.6.0 **February 07, 2024** ### What’s New - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## 1.5.1 **March 15, 2022** ### Minimum Mule Version **Mule 4.1.0** ### Fixed Issues - Error handling responses revised for JSON compliance. ## 1.5.0 **June 24, 2021** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Introduced the capability to configure timeouts when validating OAuth2 tokens for incoming requests. ## 1.4.0 **December 22, 2020** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Added support for policies to validate one or all of the scopes defined in API Manager. - Added OAS3 code snippet in the policy YAML. ## 1.3.3 **September 28, 2020** ### Minimum Mule Version **Mule 4.1.0** ### Fixed Issues - Because the `Content-Type` header of the JSON response from the validate endpoint had additional information, such as charset, the response returned was interpreted as String instead of JSON. The additional modifier is now disregarded. - Responses from the validation endpoint in which the value of the `expires_in` field was equal to 0 were not being parsed as an expired token. ## 1.3.2 **Apr 30, 2020** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. - Several performance improvements are introduced in error handling. ### Fixed Issues - After a 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). ## 1.3.1 **December 18, 2019** ### Minimum Mule Version **4.1.0** ### Fixed Issues - Authorization entity attributes that contain non-primitive values were not correctly parsed. These values are now ignored. - An error occured when an object within a JSON object was treated as String type instead of JSON type. This issue is now resolved. - The `Fault` element in the WSDL APIs now includes the `Detail` element, with additional error details. ## 1.3.0 **Sep 4, 2019** ### Minimum Mule Version **4.1.0** ### New Features and Enhancements - Introduced configuration flag to enable TLS validation on the Authorization Servers' certificates. - Added token rejection when the active field of the introspection endpoint response is 'false'. - Performance improvements. ### 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. ### Fixed Issues - Fixed expiration time field being mandatory. ## 1.2.0 **Apr 26, 2019** ### Minimum Mule Version **4.1.0** ### New Features and Enhancements - Introduces support to encrypt sensitive information related to the policy. The runtime version needs to support encryption and needs to be properly configured. - The default configuration has been modified to avoid propagating or returning policy headers unless explicitly configured by checking the "Expose headers" option. - Performance improvements. ### 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.4 **Feb 22, 2019** ### Minimum Mule Version **4.1.0** ### Fixed Issues - Fixed performance issue concerning scheduling. ## 1.1.3 **Jan 11, 2019** ### Minimum Mule Version **4.0.0** ### New Features and Enhancements - Improved the RAML and OAS snippets. ## 1.1.2 **Oct 9, 2018** ### Minimum Mule Version **4.0.0** ### Fixed Issues - Fixed `ExpressionRuntimeException` error when a WSDL proxy receives an empty payload, or an invalid XML. ## 1.1.1 **Jun 27, 2018** ### Minimum Mule Version **4.0.0** ### Fixed Issues - Fixed error preventing federated and client ID based policies to apply when a Security Manager is defined in the same app with a tracked endpoint. ## 1.1.0 **Jan 25, 2018** ### Fixed Issues - Fixed issue causing federated policies to lose query and URI parameters of the requester. ### Minimum Mule Version **4.0.0** ## 1.0.0 **Nov 14, 2017** ### Minimum Mule Version **4.0.0** ## See Also - [PingFederate OAuth 2.0 Token Enforcement Policy for Mule 4](https://docs.mulesoft.com/mule-gateway/policies-included-pingfederate-oauth-token-enforcement) - [Known Issues](https://help.salesforce.com/s/issues)