Add an exmaple/helpe for Scoped Tokens

[PhorstenkampFuzzy]

We are useing Scoped Tokens:

https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/

Logging in with via curl / postman works:

https://api.atlassian.com/ex/confluence/{{UUID}}/wiki/api/v2/spaces

But how do we configure this for the sphinx-contrib confluencebuilder?

Could you add an example to your docs or help us out directly? Does this tool suport this?

[jdknight]

Tried scope tokens for the first time just now. For sure there can be some improvements to this extension to better handle this, but it is possible with the current stable release.

(mentioning the cloud identifier fetching for others)

First, acquire the cloud identifier for the target space by venturing to:

https://<YOURSPACE>.atlassian.net/_edge/tenant_info

Update confluence_server_url to the following:

confluence_server_url = 'https://api.atlassian.com/ex/confluence/GUID/'

Replacing GUID with the GUID with the cloud identifier.

Explicitly force APIv2 mode:

confluence_api_mode = 'v2'

For the scoped API token, use the following granular scopes (should be all, will do a more complete scan later):

read:space:confluence
read:content.metadata:confluence
read:page:confluence
write:page:confluence
delete:page:confluence
read:attachment:confluence
read:content-details:confluence
write:attachment:confluence
delete:attachment:confluence
write:watcher:confluence

And lastly, ensure confluence_api_token is updated with the newly created token.

Please let me know if there is anything missing or there are other issues.

[PhorstenkampFuzzy]

The rights needed for this tool where exceptionally helpfull. Thank you. I suggest adding this to the docs.

[jdknight]

If willing/able, please take a look at the documentation updates outlined in #1134. If there is anything missing, we can add it; otherwise, the content there will be used in a future release's published documentation.

[PhorstenkampFuzzy]

Will do!