nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automatically adding users when creating issues via email handler - Can add as LDAP instead of JIRA Directory?

Andrew Midkiff

We have a project where users can send in a request via an email address and it creates a new issue in JIRA. We have it set so that if the email is not recognized, JIRA sets up an account for the user.

Right now, it sets up the account in the JIRA Directory. We'd like for it to automatically use the Delegated LDAP Directory since that's what we're using for our accounts.

Is there a way to set this up so that the auto creation uses the right directory, or will we periodically have to find all of the JIRA directory accounts and convert them in bulk?

Thanks

Accepted answers

Mikael Sandberg

It all depends on the order of your user directories. If you want the user to be created in your LDAP directory it has to be before the JIRA internal directory.

All comments

Mikael Sandberg

It all depends on the order of your user directories. If you want the user to be created in your LDAP directory it has to be before the JIRA internal directory.

Andrew Midkiff

Thanks! That explains the "order" for the directories.

crf

One small note: Not necessarily the first directory, but the first writable directory. If the first directory in the list is not configured to have writes enabled, then JIRA will move on to the next one.

The order does not only impact which one is selected for creating new users; it also determines the order in which they are searched. This can have some performance impact on systems with a large number of users (you'd normally want the directory that has most of your users in it listed first).

More importantly, if you have the same user account listed in multiple directories, the first directory that they are found in is the one that wins. That same username from the directories that follow are said to be "shadowed" and JIRA will generally ignore them, including whatever group memberships they might have.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

jira-core