Anonymous_User Absent Member.
Absent Member.
360 views

iTrac Workflow


Is it possible to have an iTrac workflow that, when started, would
update each step when another incident comes in and meets a specific
criteria? For instance, a user gets terminated and that would initiate
the workflow. When the next event comes through from a different system
(i.e., - MAD, DB, etc) it would update the workflow that a step was
completed, and once all the required events have come in, it would
automatically close the incident. I understand the workflow piece, just
not sure how to have the workflow look for and accept a new event as a
way of progressing it.

Any insight or guidance would be greatly appreciated as always!!

JK


--
jkinney
------------------------------------------------------------------------
jkinney's Profile: https://forums.netiq.com/member.php?userid=296
View this thread: https://forums.netiq.com/showthread.php?t=46412

0 Likes
2 Replies
Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: iTrac Workflow


Hi jkinney,

This is not currently possible with iTRAC workflow, although I can think
of two solutions that might work for you.

One is to use an external workflow engine such as the one built into
Identity Manager. Since correlation supports SOAP calls, you could
manipulate the external IDM workflows using that interface.

The simpler method, and probably the one closer to your use case, is not
to use a workflow at all but to use Dynamic Lists. I'll explain how we
implemented a control for "users must change their password on first use
after a reset" and I think you'll see the analogy.

What we did was as follows:
1) Created two Dynamic Lists: 'PasswordReset' and 'FirstLogin'.
2) Wrote a correlation rule that detected password resets and placed
users whose passwords were reset on the 'PasswordReset' DL.
3) Wrote another correlation rule that detected logins where a user was
on the 'PasswordReset' DL and added them to the 'FirstLogin' DL (and
removed them from the other DL).
4) Wrote another correlation rule that detected a self-password change
where the user was on the 'FirstLogin' DL and removes them from that DL.
This is the 'acceptable' condition.
5) Wrote another correlation rule that detects another login when the
user is on the 'FirstLogin' DL and generates an alert/incident.

So basically we use Dynamic Lists as a little state engine to track user
activity, and correlation rules to move users through the acceptable
states and/or alert if the correct path is not taken.


--
DCorlette
------------------------------------------------------------------------
DCorlette's Profile: https://forums.netiq.com/member.php?userid=323
View this thread: https://forums.netiq.com/showthread.php?t=46412

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iTrac Workflow


Interesting use case, and it sounds like that might suit our needs for
the time being. Ultimately, I'd love to have the tracking and
functionality the workflow/incident model would provide, but this may
work for me in the interim.

Thanks for the feedback and a very cool idea!!


Joey


--
jkinney
------------------------------------------------------------------------
jkinney's Profile: https://forums.netiq.com/member.php?userid=296
View this thread: https://forums.netiq.com/showthread.php?t=46412

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.