Management of users, groups, authentication, and directories happens outside of an organization’s primary Atlassian Cloud domain. Even if an organization uses https://org1234.atlassian.net for their Jira, all user administration happens on https://admin.atlassian.com
Atlassian has provided very little in the way of API methods by which Cloud users may be managed. For example, the quickest way to bulk-change users from one authentication policy to another is to create a CSV, and import that CSV from the front end. This is… not convenient.
Unlike domains at the organizational level, the Atlassian Admin portal doesn’t use a username and a token for authentication. Instead, it uses a cloud.session.token. When you navigate from an organizational domain to the Admin portal, this token is generated and stored as a cookie.
I haven’t yet figured out how to generate the cloud.session.token with Python. Instead, what we’re first going to do is authenticate against the admin portal in our web browser, and then “borrow” that cookie for our script. Here are the steps to do this:
- Log in to the Atlassian Cloud in your browser
- Go to https://admin.atlassian.com/
- Right-click the page, and inspect
- Open the network tab
- Refresh the page
- Locate the GET request that was sent