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.
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 ...
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