Also, moving back to bidirectional is out of the question.
The password policies are actually the same, but the problem is the
password history mostly. In our setup we can never guarantee the password histories
are in sync and users are too lazy to think up new password combinations.
Isn't there any way to properly tag or handle the status events?
Where did that extra status come from?
I'm still kind of new to the IDM world, so I can't really tell how off I am.
I can't help feeling i've missed something extremely obvious. After all,
it doesn't make sense that all edir-to-edir driver by default can't report failed password synchronizations, does it?