Summary

Request to add OAuth (scoped API token) support for the /wiki/rest/knowledge-base/1.0/permissions endpoint in Confluence Cloud, to enable secure integration with Jira Service Management Data Center (JSM DC) using service accounts.

Background & Motivation

• Current Situation:
  JSM DC integrates with Confluence Cloud to fetch knowledge base space permissions via the /wiki/rest/knowledge-base/1.0/permissions endpoint.

• Problem:
  • The endpoint currently does not support OAuth (scoped API tokens).
  • Service accounts, which require scoped tokens, receive an error:

 {{401 Unauthorized; scope does not match}} error.

• • Only classic (non-scoped) API tokens for named users work, but these are being deprecated.
• Impact:
  • Customers cannot use service accounts for secure, automated integration.
  • This blocks best-practice automation and compliance for enterprise customers.
  • It is inconsistent with Atlassian’s move towards OAuth and scoped tokens for all API access.

Request

Please add OAuth (scoped API token) support to the /wiki/rest/knowledge-base/1.0/permissions endpoint in Confluence Cloud.

• Ensure that the endpoint is included in the list of APIs that support OAuth/scoped tokens.
• Document the required scopes for accessing this endpoint.

Use Case

• Scenario:
  An enterprise customer wants to integrate JSM DC with Confluence Cloud using a service account for automated knowledge base management.

• Steps:
  1. The service account is granted appropriate Confluence Cloud permissions.
  2. JSM DC attempts to fetch space permissions using the /wiki/rest/knowledge-base/1.0/permissions endpoint with a scoped API token.
  3. The request fails with a 401 error due to a lack of OAuth support.

• Desired Outcome:
  The endpoint should accept OAuth tokens with the correct scopes, allowing service accounts to access it securely.