OAuth 2.0 Resource Server (MCP compatible auth)
Kantega SSO offers a setup that exposes Jira, Confluence, Bitbucket or Bamboo as an OAuth 2.0 resource server, allowing machine to machine communication where other applications can use JWT access tokens from an identity provider to authenticate towards Jira APIs using Kantega SSO. For example, this allows you to serve the Atlassian products as an MCP server using secure OAuth 2.0 authorization.
NOTE: this feature is still in Beta at the current stage. Use in production environment is NOT recommended without extensive testing in a staging environment.
If you require any assistance in configuring this new functionality, don’t hesitate to reach out to our support team.
Setup guides:
So far we have Entra ID as an example for setting up the integration, but in theory this should work for any OAuth 2.0 / OIDC identity provider.
Conceptual flow
The below sequence diagram highlights the conceptual flow of this OAuth 2.0 setup and searching of data from Jira, using Entra ID as the case example:
