Which of the following represents the full set of security schemes supported by the HTTP Connector?

• A. Basic Authentication, OAuth 2.0 Client Credentials, OAuth 2.0 Authorization Code, Pass Through, and Digest Authentication
• B. Basic Authentication only
• C. OAuth 2.0 Client Credentials and Digest only
• D. Digest Authentication and TLS mutual

Answer: (A)

Understanding which security schemes can be configured on the HTTP Connector in MuleSoft is tested here. The HTTP Connector supports a complete set that includes Basic Authentication, Digest Authentication, OAuth 2.0 using the Client Credentials flow, OAuth 2.0 using the Authorization Code flow, and Pass Through. Basic and Digest are standard HTTP authentication methods. OAuth 2.0 Client Credentials is used for server-to-server authentication with a client_id and client_secret. OAuth 2.0 Authorization Code supports user-involved flows with an authorization code. Pass Through means the connector forwards requests without applying its own authentication, leaving security to the backend or another layer. TLS mutual is a transport-layer security feature managed by the TLS context rather than an HTTP authorization scheme, so it isn’t counted as one of the HTTP Connector’s security schemes. That’s why the full set includes the five methods listed above, not just a subset.