Jevans78 Absent Member.
Absent Member.
647 views

Driver processing order

Hi,

I have a situation where a user is created in the vault from an Oracle HR system. This triggers the AD driver to them process the add event and provision them to AD.

The issue is that the entitlements driver sometimes does not process until after the AD driver. When this happens the AD driver veto's the event because there is no entitlement on the user object.

Does anyone know if there is a way of specifying which driver processes an event first within eDirectory? Or failing this is there a way to perhaps re-send an event through a driver to cater for these situations?

Thanks in advance

John
Labels (1)
0 Likes
2 Replies
Knowledge Partner
Knowledge Partner

Re: Driver processing order

Jevans78 wrote:

> The issue is that the entitlements driver sometimes does not process
> until after the AD driver. When this happens the AD driver veto's the
> event because there is no entitlement on the user object.
>
> Does anyone know if there is a way of specifying which driver processes
> an event first within eDirectory? Or failing this is there a way to
> perhaps re-send an event through a driver to cater for these
> situations?


IDM handle that situation by default.

When the AD driver vetoed the initial add without entitlement, the object won't
receive an association. Subsequently adding the entitlement should result in a
modify event on the subscriber that will get converted into a synthetic add and
processed as such.

If your driver does not work that way, find out if it sees a modify event when
the entitlement is added. If not, add DirXML-EntitlementRef to your subscriber
notify filter. If a modify event is seen, figure out why it's not being
converted to an add event or why that synthetic add is not processed as you
expect it to.

Post a level 3 trace if you want people here to look over it.

--
http://www.is4it.de/en/solution/identity-access-management/
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Jevans78 Absent Member.
Absent Member.

Re: Driver processing order

Brilliant thanks. The DirXML-EntitlementRef isn't in the AD driver filter, so I'll add that as a notify and see if that triggers another event. Sounds like that'll sort it, but I'll post back once I've tested.
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.