When a Basic Authentication policy is applied to an API on CloudHub but clients can still access the API without authentication, the likely cause is a missing Autodiscovery element. Here's how this affects API security:
* Autodiscovery in MuleSoft:
* The Autodiscovery element is essential for linking an API implementation deployed in CloudHub with its API instance defined in API Manager. This connection allows the policies applied in API Manager, such as Basic Authentication, to be enforced on the deployed API.
* Why Option B is Correct:
* Without Autodiscovery, the deployed application does not "know" about the policies configured in API Manager, resulting in unrestricted access. Adding Autodiscovery enables the API to enforce the policies correctly.
* Explanation of Incorrect Options:
* Option A (incorrect Exchange version) would not cause bypassing of security policies.
* Option C (missing client applications) does not impact authentication policy enforcement.
* Option D (worker restart) is irrelevant to policy enforcement.
ReferencesRefer to MuleSoft documentation on Autodiscovery configuration and linking API Manager policies for additional information on setting up secure API policies.