You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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..
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.