Issue Summary

After an Atlassian account email is updated, it will take a few minutes for the effects to propagate and allow the new email to be used with an existing API token in basic auth for REST API calls.

However, it seems the time taken for the effect to propagate is longer than we expect.

Steps to Reproduce

1. If there is no API token for an Atlassian account, create an API token
2. Check that the API token is working with the account email for a REST API call
   • Basic auth:

      old@email.com:API_token 

3. Update the Atlassian account email to a different email
4. Run the same REST API call using the old email
   • Basic auth:

      old@email.com:API_token 

5. Run the same REST API call using the new email
   • Basic auth:

      new@email.com:API_token 

Expected Results

• Basic auth using the old email with the API token should not work
• Basic auth using the new email with the API token will work
• It is expected that it should take only a few minutes (less than 10 minutes) for the changes to propagate and the above results to be observed

Actual Results

The email change seems to take longer than 10 minutes to affect API authentication

• Basic auth using the old email with the API token still works from up to 30 minutes to 3 hours after the account email update
• Basic auth using the new email with the API token does not work from up to 30 minutes to 3 hours after the account email update

Workaround

The effects of the email change will gradually take place and the same API token will work with the new email eventually.

The user can generate a new API token for their account which will work immediately with their new account email: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/#Create-an-API-token