> I have an old propriety system that I need to include in the
> provisioning. The only way I will be able to communicate with it, is
> via the cmd-connector.
> While I have got creation and deletion of both users ans groups
> working, I fail to figure out how to get a hold of the group membership.
> I don't understand how or what to map for the membership to be
> presented to the connector.
> If anyone could point me in the right direction, I would be most
great that you've been able to put the CMD connector at work, it's not
an easy beast.
The concept of "memberships" as assignment of users to groups is absent
in ConnId, it's more something that Syncope adds on top.
Some connectors (LDAP, Active Directory, ...) provide "special
attributes" with purpose of carrying out such information, but this
needs anyway some sort of special handling on Syncope side, e.g.
Propagation  and Pull  actions.
Example: the LDAP connector can be instructed, when querying for users,
to return the LDAP_GROUPS special attribute for each user, which
contains all the DNs of the groups that user is member of.
Conversely, when creating / updating an user on LDAP, Syncope can
populate the LDAP_GROUPS attribute, and the LDAP connector will take
care of assigning at LDAP level.
You can take a look at how the membership action classes work for LDAP:
 when sending during propagation and  when pulling users and groups.