You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
Hello Jira Community,
I'm encountering an issue with my Jira installation and would appreciate your help in resolving it.
- Primary Atlassian account: firstname.lastname@example.org
- Additional account: email@example.com (this account has been deleted)
1. Deleted the firstname.lastname@example.org account.
2. Changed the email of the primary account (email@example.com) to firstname.lastname@example.org.
Everything is working fine, except for the API. When I try to retrieve projects using the API, it returns an empty array, similar to the behavior of the old Jira.
Any insights or suggestions on how to resolve this API issue would be greatly appreciated.
"Everything is working fine, except for the API.'
The REST API?
It sounds like you're trying to use the old token from the old account to authentication the session, not the new token for the new account. Are you sure you're getting an 'empty array' back, not a 401 authentication failure error code?
A GET request to the Get current user endpoint will give you an immediate answer if the REST API server is accepting whatever credentials you are providing and will echo back who it thinks you are.
You said you created a 'another' key, but you can't do that, you can only create TOKENS.
If you are using key + token to authenticate via BASIC auth for Jira Cloud, then your email address is the KEY, so that infers you are using your email address + token to authenticate.
Tokens are immutably linked to unique keys. If the key is an email address and you change that email address, then you change the key's uniqueness, and now whatever token is associated with it is useless.
You must discard the old token associated with the old email address that you previously used to login to Jira Cloud and generate an entirely new token associated with the new email address you are now using to log in, then use that new key + token pair in your authentication session.