memberOf / isMemberOf support. about redmine_ldap_sync HOT 10 CLOSED

Yes, it would require two requests to ldap.
One to fetch the user and groups and a second one to get the groups names.

It would have to be optional to prevent breaking the support for other ldap servers.

If I have the time I'll have a look.

from redmine_ldap_sync.

Thanks for the response. I hope you can help me with this. If I can help you in any way please let me know.

from redmine_ldap_sync.

JellHissink, I've just added the new feature.

I would be glad to hear your comments.

Don't forget to run rake db;migrate_plugins RAILS_ENV={env}.

from redmine_ldap_sync.

Tomorrow I'll also update the readme with the new changes.

from redmine_ldap_sync.

Seems as new filed won't show up for all already configured ödap server's. I have 3 servers configured any only one shows new options. Waiting for doc of the new options, cause unsure what they really do.
I Thing i will choose "Groupmembership: on the user class" and set "Members attribute (group)" to the attribute name in the group class which indetifies user of this group and "Memberid attribute (user)" to attribute name of the user's class, which indetifies the groups the user's belonks to.
I could also choose "Groupmembership: on the group class", but why should i do else. In my case referencing works both way (user<>group), so choose user, because better perfoemance?
Tx for contributing.
..should make it into the core btw.

from redmine_ldap_sync.

You're right.
I've made a mistake on the elements ids as I didn't count with multiple servers, as so, there is a conflict between the ids.

The performace should be almost the same as I didn't manage to reduce the number of calls to the ldap server.
The main difference is, according to what JalleHissink said, nested groups.

This means that, if you have a group A belonging to a B and an user belonging to the group A, at least in OpenDS, the following occurs:

• If you set group membership on the user class, the user will be member of both group A and B.
• If you set group membership on the group class, the user will only be member of group B.

from redmine_ldap_sync.

cforce, I've just commited a fix for the problem you reported.

from redmine_ldap_sync.

Thorin, thanks for taking the time to implement this. I'll test it this week

from redmine_ldap_sync.

Hi Thorin,
It works for me now, had some problems with the groupid attribute, for OpenDS you should set it to entryDN. Took some debugging with puts, but found it.
My settings if somebody wants to use OpenDS:

• Group base DN: dc=CodeWise,dc=nl
• Group name attribute: cn
• Group membership: On the user class
• Groups attribute (user): isMemberOf
• Groupid attribute (group): entryDN
• Users objectclass: person
• Groups objectclass: groupOfUniqueNames
• Group name pattern:
• Group search filter:

Thanks again for the change!

from redmine_ldap_sync.

I've added your OpenDS configuration to the README.md. Thanks

from redmine_ldap_sync.