[stable9] New command to update group mappings

[jvillafanez]

Description

New command to update LDAP group mappings

Related Issue

https://github.com/owncloud/enterprise/issues/1464
Backport of owncloud/user_ldap#14 to stable9

Motivation and Context

How Has This Been Tested?

Run the command against an LDAP server

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[mention-bot]

@jvillafanez, thanks for your PR! By analyzing the history of the files in this pull request, we identified @blizzz, @owncloud-bot and @DeepDiver1975 to be potential reviewers.

[PVince81]

Doesn't seem to work, I have setup LDAP like I did for the master PR but the command says the groups are unknown:

± % occ ldap:update-group Box10 Box100
Group membership attribute is critical for this command, please verify.
* localhost:389 -> memberUid
Some of the groups are unknown

In the users page I can see these groups visible, so something must be wrong.

[PVince81]

Both oc_ldap_group_mapping and oc_ldap_group_members contain entries.

[PVince81]

Hmm, weird. I upgraded to master and it doesn't work there either.

[PVince81]

Ohhh even stranger, the checkGroupMappingExists receives 2 results for the group which is not equal to the count of 1, so fails... But the entry only exists once in the DB.

[PVince81]

Ah... I passed two groups on the CLI. One exists in the mapping but one doesn't... Ok, I should have read the error message properly. Turns out I deleted Box100 in a previous test run.

Will retest...

[PVince81]

Works now 👍

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.