README revision b0663f520f7ec2df9447b5cc08c44a1029642a8d
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncThe sample is the same as sample 2b except that it focuses on one special attribute, ldapGroups, which is used to synchronized ldap group memberships of users
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncThe sample configuration connects to a local OpenDJ with the following paramers:
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync"host" : "localhost",
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync"port" : 1389,
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync"principal" : "cn=Directory Manager",
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsync"credentials" : "password",
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncIn opposite to sample2, this sample sync.json configuration contains two mappings from OpenDJ to OpenIDM and back.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncThe number of attributes mapped are still rather limited.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncIt contains a scheduler configuration which can be used to schedule reconciliation.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncNew users will be created from LDAP or existing will be updated and back-linked from OpenIDM to OpenDJ
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncChanges on OpenIDM will now be pushed into the LDAP server!
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncIn addition to sample 2b it will sync ldap group membership:
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncAdd a user to an ldap group and run sync: a new attribute will be filled in the user's json representation in the repo, ldapGroups, which contains a list of the groups dns where the user is a memberOf.
4fd606d1f5abe38e1f42c38de1d2e895166bd0f4vboxsyncFor a more precise description on how to run the sample see: