Why nesting of internal groups does not work for AD users?

Here is scenario:

There are 2 directories in JIRA (v. 6.2.7):  first is internal and another is from AD (with option "Read Only, with Local Groups", nesting is enabled)

 

There are two users: INT (in internal dir)  and AD (from active-directory/LDAP dir), 


and two groups, defined in JIRA: A and AA (AA is nested into A).

 

Both users INT and AD are members of  AA group.

 

In JIRA instance, user INT is attributed to A group (as expected) , but user AD is NOT in A group (that is strange). I.e, group A is not shown in group list for  AD user at Users page, and JIRA does not recognize AD as a member of A group in schemes, projects, etc.

 

In Confluence instance, that uses JIRA as directory provider, both INT and AD users attributed to A group as well as to AA.

Why does it work this way and how to make it working as expected? (Both AD and IND users shall be attributed to A group in JIRA)?

1 answer

1 accepted

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,755 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot