# OAuth 2.0 Authorization Code Credential Provider now available

Aembit now supports 3-legged OAuth (3LO) workflows through the new OAuth 2.0 Authorization Code Credential Provider. Applications can request a user’s permission to access their account data and act on the user’s behalf.

With 3LO support, an application can access services or applications that the user has authorized.

Aembit supports the following third-party services with OAuth 2.0 Authorization Code Credential Providers:

* [Atlassian](https://developer.atlassian.com/cloud/confluence/oauth-2-3lo-apps/)
* [GitLab](https://docs.gitlab.com/ee/api/oauth2.html)
* [Slack](https://api.slack.com/legacy/oauth)
* [GCP BigQuery](https://cloud.google.com/bigquery/docs/third-party-integration#authentication)
* [Apigee](https://docs.apigee.com/api-platform/security/oauth/oauth-introduction)
* [PagerDuty](https://www.pagerduty.com/blog/build-sophisticated-apps-for-your-pagerduty-environment-using-oauth-2-0-and-api-scopes/)

For configuration details, see the [OAuth 2.0 Authorization Code Credential](/user-guide/access-policies/credential-providers/oauth-authorization-code) documentation.

An expansion to Client Workload identification and Trust Provider match rules also shipped in this release; see [Expanded Client Workload identification and Trust Provider match rules](/changelog/entry/2024-06-26-expanded-client-workload-identification-and-trust-provider-match-rules).