Contact Us 1-800-596-4880
  1. Homepage
  2. Mule Runtime (4.1)
  3. Security

  4. Mule Secure Token Service

Mule Secure Token Service OAuth 2.0

Standard Support for Mule 4.1 ended on November 2, 2020, and this version of Mule reached its End of Life on November 2, 2022, when Extended Support ended.

Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted.

MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements.

The Mule runtime engine supports the OAuth 2.0 protocol. The way to configure OAuth 2.0 authorization differs, depending on the OAuth role and your objective:

  • Configure authentication in your client Mule app when sending requests to a service that requires authentication, such as the Github OAuth2 server. Use the OAuth Module for the OAuth2 configuration.

  • Use the Mule OAuth2 Provider Connector to create a Mule application that grants and validates the tokens needed to access a protected resource.

To protect your API or app from receiving unauthorized requests, use an API Manager policy, such as the OAuth 2.0 Access Token Enforcement Using External Provider policy. To expose a web service protected by OAuth 2.0 security, see the API Manager documentation.

See Also