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

Deleting shadow users with ScriptRunner

tl;dr: I want to delete shadow users in the Jira 'internal' directory that are currently authenticating against an external directory.

Past threads that come close to this request talk about database operations a lot, and they're many years old. I know the two ways to do this are both pretty gross, like:

1) Disable or rename users in the primary directory to expose the old internal users again, and delete them, or

2) Delete from the database, being sure to hit cwd_users and cwd_memberships.

But what about with ScriptRunner? Most of the interfaces are obsessively focused on ApplicationUsers, which isn't helpful (doesn't return shadow users). I can get to a directory-level user via the embedded Crowd interface, but none of those interfaces seem to have user deletion methods.

Is ScriptRunner a dead end or am I missing something? Is a database operation still the only way to do this?

=======

Situation (and why I'm not just "ignore them, they aren't hurting anything") -- we're ditching Crowd and migrating back to Jira internal users. Since we originally migrated from Jira internal to Crowd, many present day users still exist, but with severely outdated info. Rather than reactive and figure those out, it seems simpler to nuke the old internal accounts and copy their up-to-date equivalents over fresh.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

172 views 0 6
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