Migrated Crowd from PROD to Dev server, Dev apps secondary admin auth goes to PROD crowd

Weird problem here -- back in the spring, I migrated my PROD Crowd to a Dev server and pointed my Dev apps to the Dev Crowd. All worked except for secondary admin auth, which I worked around in Dev Confluence (see https://answers.atlassian.com/questions/168573/cannot-authenticate-to-crowd-as-administrator-in-confluence?page=1). Same thing happens with Dev Jira now, and I discovered that in the PROD Crowd catalina.out file whenever I tried to get into Dev Jira administration (for example, to re-index), when I got to the secondary authorization, I get "Client with address "" [my Dev Jira box] is forbidden from making requests to the application, {2}" message (and in my Dev Jira browser, I get the "Oops!" page with stack trace. So somewhere my Dev Jira (and Confluence) are pointing back at PROD Crowd. I'm guessing there is something amiss with the DEV Crowd config. Ideas?

2 answers

Have you added your DEV Jira to the list of allowed remote addresses in your DEV Crowd for the application?

As Andrew explaine before you can cchekc and add your DEv Jira IP Address going to Application tab > select the directory > Remote Addresses.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Jira

How you can achieve compact and easy-to-maintain workflows in your JIRA( Server)

This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...

284 views 0 0
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you