README revision 1e5b453044798c6ea2d0ec818f64fa8e0b5f05dd
d2236df2116a3cbe8b17c567f4a9c2281733a956vboxsyncThe sample configuration connects to a local OpenDJ with the following paramers:
d2236df2116a3cbe8b17c567f4a9c2281733a956vboxsync"host" : "localhost",
d2236df2116a3cbe8b17c567f4a9c2281733a956vboxsync"port" : 1389,
d2236df2116a3cbe8b17c567f4a9c2281733a956vboxsync"principal" : "cn=Directory Manager",
d2236df2116a3cbe8b17c567f4a9c2281733a956vboxsync"credentials" : "password",
d2236df2116a3cbe8b17c567f4a9c2281733a956vboxsyncIn opposite to sample2, this sample sync.json configuration contains two mappings from OpenDJ to OpenIDM and back.
fcae7923a3c756b333f1e33eba002edf4448fb54vboxsyncThe number of attributes mapped are still rather limited.
fcae7923a3c756b333f1e33eba002edf4448fb54vboxsyncIt contains a scheduler configuration which can be used to schedule reconciliation.
fcae7923a3c756b333f1e33eba002edf4448fb54vboxsyncNew users will be created from LDAP or existing will be updated and back-linked from OpenIDM to OpenDJ
fcae7923a3c756b333f1e33eba002edf4448fb54vboxsyncChanges on OpenIDM will now be pushed into the LDAP server!