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

Your Points Tracker
  • 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
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?
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

User Import with attributes Edited

I want to import approximately 350 users into crowd with CSV files.

The problem is, I also have a custom attribute associated with each user.

Originally, I had intended to just use the CSV import process, and then add the attribute using SQL.

HOWEVER, I have no idea how to generate the ID because it is NOT a SQL Sequence, it is a Hibernate value generated by com.atlassian.hibernate.extras.ResettableTableHiLoGenerator.

Any recommendations? seq_userimport perhaps?

1 answer

1 vote

Hi Robert,

I usually try to avoid messing with the database as much as possible as this could screw things up pretty bad. When I'm doing bulk stuff in Crowd, I often use the REST api in combination with Postman runners.

For adding an attribute you could use a POST call to /rest/usermanagement/1/user/attribute?username={username} and add the attribute info to the body of that request:

{ "attributes": [ { "name": "invalidPasswordAttempts", "values": [ "0" ] }, { "name": "requiresPasswordChange", "values": [ "false" ] } ] }

Using Postman Runner you can use a csv as input and easily add attributes for hunderds of users.

Hope this helps.



Regrettably, the way our environment is configured prevents me from using the Crowd REST API. I do not control the configuration, InfoSec does.

Hey Robert,

Maarten's suggestion is definitely the approach I'd take, however if infosec have blocked REST API, then this isn't an option.

I doubt infosec would be very happy with direct DB changes if they don't even like you using the API. Maybe worth discussing with infosec if you can get a temporary exemption while you setup the accounts?

Otherwise, you might be able to automate the attribute population via a record/playback tool - something like Microsoft Power Automate Desktop or Selenium and automate the steps you'd be doing manually


Suggest an answer

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

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

292 views 16 18
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