Rule Auditing - Discussion

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

8.4

Share all details about your problem, including any error messages you may have received.

The default audit logs for “Disablement” are kind of ‘bleh’, and I need more visibility. For example, if I have a custom rule that disables users based on criteria, then I want to know in the audit log which rule caused it (that way if the logic is broken, then I can easily find out why). I am trying to set the “Source” field as the rule name. However, I am having issues. Would the correct call be:

context.getTask().getRule().getName()

If I am in the Rule source code, I want to dynamically get the name of the rule. That way I don’t have to hardcode it and remember to change it.

I want to hear other’s opinions on how to Audit and debug properly.

2

its easier to crate a custom Audit event for RuleExecution and have a method somewhere that logs the rule execution Ex:
-=-=-=-=-=-
boolean audit = auditRuleExecution(“Rulename”);

3

Great suggestion! I am doing something very similar. However, I want to avoid hardcoding the rule name so that the logic updates if I need to change the rule name itself. So when the task is executing the rule, I want the rule to ‘audit itself’ when it takes an action on a user.

4

Hardcoding is not bad as would be easier to reference, as context runs alot of stuff at the same time.