How do Public/Private keys work with Nds2Nds Password Sync

[jsam...@vansd.org]

Hi

What effect do the public/private key pairs have
when creating/modifying users in an Nds2Nds driver
environment.

I've read TID: 10085614 but it is not making
sense right now.
//---------------------------------
TID: 10085614
Problem:
For this scenario to happen, a user must exist in the destination tree
of the merge and the user on the source tree must have been created
with an application that provided the password on creation. When
the user is created in the source tree it initially gets created without the
password, so when the add is sent, there is no password yet. The
merge happens and at some point the password creation happens
causing a modify which causes the swap. So by having a create rule
on the Subscriber the add is vetoed and then when the password is
created it will send it across and merge successfully with the password
this time.
Fix:
The fix for the password swap on a merge of an object is to have a
create rule on the Subscriber Channel that requires the Public Key
Attribute for User.
//---------------------------------

Thanks in advance.