Unable to login to staging Jira when using Crowd User Management after creating from the snapshot

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Replicating JIRA instance using a snapshot of JIRA production, to create a staging JIRA Instance. JIRA is connected using Crowd User management. When the users belong to the Crowd user management tried to login in the staging instance:

  • It shows as invalid login.

  • Redirected to the login screen without any error.

  • Internal directory users can log in successfully.

Diagnosis

Environment

  • JIRA instance that connected through Crowd User Management.

Diagnostic Steps

  • Confirmed if the JIRA staging application name is set up in Crowd.

  • Login as JIRA Internal Administrator and confirm if the User Directories settings connected using the JIRA staging application name in Crowd.

Cause

After creating JIRA staging from the snapshot, it is still connected through Crowd User management using JIRA production settings.

Solution

  1. Add a new application in Crowd that contains JIRA staging URL.

    (Auto-migrated image: description temporarily unavailable)
  2. Reconfigure Crowd User Directories settings in JIRA to connect to JIRA staging URL.

    (Auto-migrated image: description temporarily unavailable)

Updated on April 15, 2025

Still need help?

The Atlassian Community is here for you.