An API is protected with a Client ID Enforcement policy and uses the default configuration. Access is requested for the client application to the API, and an approved
contract now exists between the client application and the API
How can a consumer of this API avoid a 401 error "Unauthorized or invalid client application credentials"?
When using the Client ID Enforcement policy with default settings, MuleSoft expects the client_id and client_secret to be provided in the URI parameters of each request. This policy is typically used to control and monitor access by validating that each request has valid credentials. Here's how to avoid a 401 Unauthorized error:
URI Parameters Requirement:
The default configuration for the Client ID Enforcement policy requires the client_id and client_secret to be included in each request's URI parameters. This is a straightforward way to authenticate API requests without additional configurations.
Why Option C is Correct:
Providing client_id and client_secret in the URI parameters meets the policy's requirements for each request, ensuring authorized access and avoiding the 401 error.
of Incorrect Options:
Option A (sending a token in the header) would be applicable for token-based authentication (like OAuth 2.0), not Client ID Enforcement.
Option B (request body) and Option D (header) are not valid locations for client_id and client_secret under the default configuration of Client ID Enforcement, which expects them in the URI.
Reference For more details, consult MuleSoft's documentation on Client ID Enforcement policies and expected request configurations
Micah
29 days agoJoanne
11 days agoDewitt
17 days agoSunshine
1 months agoGabriele
21 days agoJamal
23 days agoElfrieda
1 months agoVicky
16 hours agoGwenn
6 days agoJunita
14 days agoArdella
17 days agoLasandra
2 months agoLamonica
3 days agoDean
25 days agoAntonio
29 days agoJospeh
30 days agoTiffiny
2 months agoSherita
2 months agoGerman
1 months agoKimbery
1 months agoMaybelle
2 months agoMatthew
2 months ago