Jira and Confluence Audit Scope API Updates

[jackbaz]

Hi,

https://support.atlassian.com/confluence/kb/scoped-api-tokens-in-confluence-cloud/

At current the only way we have been able to get confluence or Jira using CCF working in Sentinel is through the classic API Token for both Atlassian and Jira. As per the above Atlassian document, scoped tokens call a separate endpoint requiring the cloudID.

Is there a new or update for the connector currently in private preview or on the road map to accommodate the above?

Thanks!

[v-utpalkumar]

Hello @jackbaz, thank you for highlighting this. We’ll review it and get back to you with some updates. Thanks!

[eemil]

I've gotten the connector to work with scoped tokens. Just had to use a slightly different organization URL: api.atlassian.com/ex/confluence/<cloud_id> for Confluence and api.atlassian.com/ex/jira/<cloud_id> for Jira.

[v-krishnachi]

@jackbaz , you can feel free to try as mentioned above with scoped tokens (eemil comments above).

1. Jira — works with "api.atlassian.com/ex/jira/{cloudId}" because the suffix /rest/api/3/auditing/record is appended cleanly. So scoped api token calls go through gateway https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/auditing/record
2. Confluence — also works "api.atlassian.com/ex/confluence/{cloudId}" because the path /wiki/rest/api/audit is appended.
   So scoped api token calls go through gateway of Confluence: https://api.atlassian.com/ex/confluence/{cloudId}/wiki/rest/api/audit

having said that the classic-token URL (.atlassian.net) is also still valid. Please let us know if you have any questions?

Apologies for the delay in responding to the ticket.

Please confirm here if the solution working.