Authentication failing in JIRA with crowd

After launching new instance from the production snapshot, made a change on database from old crowd server domain to new crowd server domain on cwd_directory_attribute but still someone new instance is still sending request to old crowd server for authentication.

What am i missing?

Seeing following in logs

3.253.130 /rest/gadget/1.0/login The user 'XXX' is required to answer a CAPTCHA elevated security check.  Failure count equals 7

1 answer

Seems that if I want to change crowd server domain that JIRA authenticates, I need to update crowd.properties file to update domain.

It's located in different place than db config file location.

../WEB-INF/class/crowd.properties

 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

24,446 views 2 7
Join discussion

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