Highlighted
Respected Contributor.
Respected Contributor.

Re: Clear Manager Attribute from AD upon Termination

Ok that makes sense, in the past I wondered why we had to call both source and dest on the AD SUB channel to see it update in IDV and AD, this explains why.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Clear Manager Attribute from AD upon Termination

In my experience, most of the time if you end up calling something that
clears source and dest then that may be a good indicator of something that
should go somewhere else, usually into business logic, as it implies you
are doing non-synchronization (but rather, business-y) thinking in the
driver config. That's fine for a business logic driver config whose sole
purpose is to apply thought, but not so great for a synchronization driver
whose sole purpose is to get stuff from here to there.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Clear Manager Attribute from AD upon Termination

On 6/12/2018 4:49 PM, ab wrote:
> In my experience, most of the time if you end up calling something that
> clears source and dest then that may be a good indicator of something that
> should go somewhere else, usually into business logic, as it implies you
> are doing non-synchronization (but rather, business-y) thinking in the
> driver config. That's fine for a business logic driver config whose sole
> purpose is to apply thought, but not so great for a synchronization driver
> whose sole purpose is to get stuff from here to there.


Very good point. It is a good indicator of moving it elsewhere.


0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Clear Manager Attribute from AD upon Termination

On 6/12/2018 3:56 PM, cosborne wrote:
>
> Ok that makes sense, in the past I wondered why we had to call both
> source and dest on the AD SUB channel to see it update in IDV and AD,
> this explains why.


And Aaron's suggestion to move teh logic out of this driver, and just
write once to the vault, which then flows where ever it should is a
better approach, regardless.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.