Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Changing CROWD "Remote Addresses" through database?

Hi,

We just switched our network to a new range of IP's. I forgot all about adding this new range of IPs to crowd under "Remote Addresses" and now I am locked out.

I have made LDAP changes manually in the database by updating the stuff I believe in "cwd_directory_attribute"

Is there any table that keeps track of the remote addresses allowed to login? I would really like to just modify the existing IP address to be that of the new network.

I would really like to do this through the database because otherwise I need to give them the old network addresses, login, add the new network address to the "Remote Addresses" and then change all the IPs to the new network again.

Tanks for any help..

1 answer

Got it. Funny, I have been looking for this on and off for a very long time. But right after asking the question, I finally find it.

It is in the crowd database under cwd_application_address

Hope it helps someone

Glad you got it sorted. For anybody else who runs into this, this is a manifestation of CWD-2315; that issue has more information on fixing the problem, and you may like to vote on the issue to have the underlying cause fixed.

As always, if you have an urgent issue (e.g. you have been locked out of your production Crowd instance), please do not hesitate to create a support issue so our support team can help you resolve the issue.

Yeah, another thing I started doing now to prevent this is adding the hostname of the servers under Remote Addresses.. I don't think localhost would work, but something that resolves to the IP you're hitting crowd on

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

306 views 9 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you