Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to regenerate External id in crowd application

Hi team,

I would like to know How to regenerate External id for users in crowd application.

If anybody know the steps or document for that Kindly share to me.


Thanks and Regards


2 answers

Maybe you will find your answer in this guide

Also I can recommend you if you use Connector type of directory try to synchronise directory. It should help

I can't find what is external_id in the spec, but as I know, it's the field by which you tell Crowd, that your user_A (from Crowd) is linked to one of your users from directory. 
Description from the Crowd: "The attribute field to use for tracking user identity across user renames". So for example, if you rename your user, Crowd will find your user by this field.
And better to use unique identifier, for example in LDAP it's uid field, and for AD - entryUUID field

Hi @Peruma Chinnasamy  and welcome to the community. 

Can you please describe your problem more clearly? How I can achieve your state? What version of Crowd do you use? And what exactly going wrong with your external id?

Hi Roman,

I was upgraded crowd v 3.7 into 4.4.0 version in non prod crowd application. In 4.4.0 version few old user  facing login issue. Those who are having the external id >32 characters. So we are planning to regenerate the external id those who are having external id >32 characters  to avoid login issue. 

Thanks and Regards


Which type of directory do you have?

We have LL AD and LL EXT directory.

When you adding a directory, you can select one of it type from this fields:
Screenshot 2022-06-07 at 14.02.42.png

Also you can check it type from DB: cwd_directory table, directory_type field

The directory type is "Delegated Authentication"

Ok, great! So that should be easier:) 

You can delete user_A from Crowd (better to do it from UI). It will not affect your user from directory.
And after you login to application with user_A it should appear in Crowd and have correct external_id.

Hi Roman,

Thank you for your valuable input.

I would like to mention few thing here.

More than 10 thousand user will face this login issue after prod crowd 4.4.0 version.

So I need fix before upgrading prod crowd. Any other fix is there doing bulk external Id regeneration.


Thanks and Regards


Ok, so one of possible solutions is to re-add directory.
Or try to use connector type of directory, which will help to resolve issues like this with synchronization feature (unfortunately there is no synchronization in Delegated).


Hope that will resolve the issue.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events