Force new users to be assigned to default LDAP group Confluence

[saiprakash_avula]

Hi my confluence is connected to LDAP server where we centrally manage Users and Group.

I had a LDAP group "confluence-users" added to Global-Permissions and in User Directories also selected LDAP Permissions ---> Read only, with Local Groups and added "confluence-users" group to Default Group Memberships.

But when a new user is added they get automatically assigned to another "xyzzy-group" available in LDAP. Please suggest if there is any turn around to force new users to a particular LDAP group.

Thanks,

Sai 

[Jonathan Smith]

User Directories was such a pain for my first year. I had to chat with Atlassian support and SAML SSO vendor to figure this puppy out.

We created confluence-users group in Active Directory. This group is marked "can use" in global permissions just like how you have it.

We then have various groups nested within confluence-users (i.e. Confluence_Internet Confluence_Merchandising etc). Because of this, default group membership in the user directory setting is blank in our environment.

Seems like a lot of our environments are different, but here is a screenshot of our settings just incase you want to try something out.

[Jonathan Smith]

Note: My setting does not set the default group once a user joins Confluence, that is handled upstream with the nested group examples.

[saiprakash_avula]

Hi Jonathan, Thanks for trying to help me

I have followed all the steps to enable nested loops and remove from Default Group membership as well added the group to global permissions but still face the same issue. Can you please let me know if there is any other turn around. I'am using OpenLDAP server to connect.

[Jonathan Smith]

@saiprakash_avulaAre you just trying to make sure confluence-users is added to their LDAP permissions automagically?

On the active directory side, when a user is put into their category, they will inherit confluence-users (which is added in the Confluence global permissions)

Setting up internal directories can be tricky since all our environments are different. It might be worthwhile to create a support request with Atlassian if  you are in a time crunch.