Document server= kwarg for dedicated tenant of Jira Cloud, and difference when using Scoped API Token #2368
Description
Problem trying to solve
Hello!
I recently spent a few hours to understand why the jira client couldn't connect to my jira cloud tenant.
I was previously using (legacy) api token (that give full rights on Jira) and passing server="https://foobar.atlassian.net" was working perfectly.
I then tried to switch to using scoped api token (that give only limited rights on Jira), and I was always getting an authentication error.
The issue is that for Scoped API Tokens the server= URL is not the same as when using the old (legacy) API Tokens.
Instead we need to use something like https://api.atlassian.com/ex/jira/{cloudId} where {cloudId} comes from https://foobar.atlassian.net/_edge/tenant_info (outputs a json with the cloudId).
See: https://jira.atlassian.com/browse/CLOUD-12617
Possible solution(s)
TSIA
There should also be a link to that new documentation in the section about api token connection
Alternatives
No response
Additional Context
No response