Basic Authentication - Simple

Fix policy schema not allowing additional properties via REST API.

First Flex compatible Policy.

Separated Policy Definition from Policy Implementation. Stronger validations applied to a given policy configuration.

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.

After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity:

Several performance improvements are introduced in this release.

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.

Introduced support to encrypt sensitive information related to the policy. The runtime version must support encryption and must be properly configured. Encryption is supported since Mule Runtime v4.2.0.

Several performance improvements are introduced.

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.

When a WSDL proxy receives an empty payload, or an invalid XML, an ExpressionRuntimeException error is generated.

When Mule is redeployed, the basic auth policies do not work.

GroupId missing for proxy samples dependency.

When an Authorization header is malformed, a 500 status code is returned instead of 401.