Repeated “Invalid Password” Prompts

[Mukul]

Hello Atlassian Community,

I am facing a persistent and confusing authentication issue while using multiple Jira Cloud portals, and I’m hoping someone here has encountered this before or can suggest a proper solution.

In our environment, we work with multiple Jira Cloud instances hosted under different domains, for example:

• abc.atlassian.net

• xyz.atlassian.net

Both portals are actively used, sometimes on the same day, and often from different devices such as a laptop and an office desktop.

Problem Description

When I log in to one Jira portal (say abc.atlassian.net) using my Atlassian account, the login works fine. However, when I then try to log in to another Jira portal (xyz.atlassian.net) in the same browser, Jira frequently reports that my password is invalid. This happens even though:

• I am using the same email address

• I am entering the correct password

• The password has not been changed manually

Because of this, I am forced to reset my password. The reset works, and I can log in successfully. However, the problem does not stop there.

Reproducible Scenario

Here’s a simple example that happens repeatedly:

• Monday: I log in to Jira (abc.atlassian.net) on my laptop → works fine

• Tuesday: I go to the office and try to log in on my desktop → Jira says my password is invalid → I reset it

• When I return to my laptop and try logging in with the same new password, Jira again says the password is invalid → forcing another reset

This cycle repeats every time I switch:

• Between devices (laptop ↔ desktop)

• Or between Jira portals (abc.atlassian.net ↔ xyz.atlassian.net)

• Or sometimes even between browsers on the same machine

Temporary Workaround (Not Ideal)

The only temporary workaround I’ve found is to:

• Use separate browsers for each Jira portal (for example, Chrome for one, Firefox for another)

While this works, it is clearly not a scalable or ideal solution. Today I may have 2 Jira portals, but in the future I could easily have 5–10 portals, and using a separate browser for each one is not practical.

Questions

1. Is this a known issue with Atlassian session handling, cookies, or SSO across multiple Jira Cloud instances?

2. Is Atlassian invalidating sessions or credentials when switching between portals or devices?

3. Is there a recommended configuration (SSO, Atlassian Access, browser settings, or cookie isolation) to avoid this behavior?

4. Has anyone found a permanent fix that allows multiple Jira Cloud portals to be used in the same browser without repeated password resets?

Any guidance, official documentation, or real-world experience would be greatly appreciated, as this issue significantly impacts daily productivity.

Thank you in advance for your help.

[Marc -Devoteam-]

Hi @Mukul 

This should work, as I use my company mail address in multiple Jira instances under different domain and access all sites in the same browser.

It could also be related to the to the policy set in each Atlassian domain administration.

I think you should reach out to the admins or if you have access yourself, remove your account from an instance and re-add it.

[Tomislav Tobijas]

Hi @Mukul ,

Atlassian Cloud auth is designed so that your Atlassian account (email/password or SSO) should work seamlessly across all Atlassian Cloud products and instances > more on that here.

Now, if your org uses SAML SSO (via Atlassian Guard), session handling and authentication are managed by your IdP. But it might be that if SSO is not consistently configured across all instances, or if there are mismatches in auth policies, you may encounter login issues.

🤔 Also, as you cannot have 2 or more Atlassian accounts using the same email address, I'm thinking maybe you're referring to a portal-only customer account. Info about that here:

• Manage portal-only customers 
• What different account types can customers have? 

This could also be an issue with session or cookie isolation, so you could try using an incognito window or a different browser to see how things will behave there 👀

Now, if both sites are managed by the same department/team, I would recommend reaching out to your IT support team within the organization, as they can check your account statuses and see how authentications are configured.  👈
If they cannot troubleshoot it themselves, someone from their staff could raise an official ticket here and get support directly from Atlassian.

Cheers,
Tobi