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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,323 views 14 20
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot