Basic Authentication - LDAP

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.

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.

Improved error handling for LDAP server validation errors and user authentication errors with appropriate error messages. The application generated a 401 error for both LDAP server authentication problems and incorrect user credentials provided by the user. The application now generates error 500 for LDAP server authentication errors. When incorrect user credentials are provided, error 401 is generated.

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 be properly configured and must support encryption. Encryption is supported starting with Mule Runtime v4.2.0.

Several performance improvements are introduced.

Reduced policy weight.

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.

Added subtree search scope.

Reduced error-handling verbosity in templates.

Improved error message verbiage for the invalid server scheme error.

When an Authorization header is malformed, a 500 status code was returned instead of 401. This issue is now resolved.