Confluence doesn't respect directory order while creating a group when connected to Crowd or Jira Directory

Issue Summary

Confluence creates a group in Crowd or Jira, even it their directory order is lower.

Environment

• Confluence 7.0.1
• Crowd 3.5.0
• Jira 8.3.3

Steps to Reproduce

1. Create a User Server in Jira
2. Connect Confluence as a User Server to Jira
3. Give this directory Read/Write permissions
4. From the Directory Order in Confluence, make sure that Jira is at the second priority
   • Internal Directory should be highest
5. Create a group in Confluence

Expected Results

Group should only be created in Confluence's Internal Directory, as all operations should be executed on the highest ordered directory

Actual Results

Group is created in Jira's directory

Notes

The same steps can be repeated for Crowd as well. Creating a group in Confluence will result in a group in Crowd, even though Crowd directory has a lower order

Notes

This behaviour is not according to our guidelines about Multiple Directories ,

Changes to users and groups will be made only in the first directory where the application has permission to make changes.

This also causes other unexpected issues if Jira or Crowd is connected to other LDAP servers because of daisy chained group propagation.