...
Once this is completed your confluence application integration as described in insert Initial Setup here and insert space admin settings here. https://thepluginpeople.atlassian.net/wiki/spaces/CSUM/pages/2424700956/Integrating+Atlassian+Crowd#Initial-Setup and https://thepluginpeople.atlassian.net/wiki/spaces/CSUM/pages/2424700956/Integrating+Atlassian+Crowd#Settings-for-Crowd-Space-Admin-Directories You will need to synchronise directory(s) you want to integrate to confluence by following this documentation: https://confluence.atlassian.com/doc/synchronizing-data-from-external-directories-229838498.html
...
Add a Directory with the type Connector and click Next
Add the initial Details
Complete the Connector Configuration
1 - Make sure that the type is OpenLDAP
2 - This is your LDAP Server Urlldap://<domain url>:<port number>exampleldap://example.com:390
3 - Manage Groups Locally Enabling this setting is recommeded if your LDAP is read only as this will create the directories to be managed locally.
4 - Username of theComplete the User and Group Configurations
Example User Configuration
Example Group Configuration
Finally setup the directory permission. If the directory is for a space admin group please refer to https://thepluginpeople.atlassian.net/wiki/spaces/CSUM/pages/2424700956/Integrating+Atlassian+Crowd#Settings-for-Crowd-Space-Admin-Directories to ensure appropriate permissions/access.
LDAP Read-Only Restrictions with Crowd
...
Even if the setting as described in Insert Example LDAP Active Directory Setup link here https://thepluginpeople.atlassian.net/wiki/spaces/CSUM/pages/2424700956/Integrating+Atlassian+Crowd#Example-LDAP-Active-Directory-Setup is set. If the group was created before this setting was activated meaning that it’s directly linked to the LDAP group then neither Crowd, Confluence or CSUM have the permission to delete/modify this group or user. This is as expected.
...