Can we configure FIM Portal to not accept unsatisfactory inputs from other sources for an attribute that is set to some validation in Portal?

Hi Guys,

We have a situation where Owner for a group should be Active, Enabled and Employee of the organization. We can set this criteria in Search Scope.

But when I try setting the Owner(who does not meet the required conditions) via PowerShell script or via sync from AD-->MV-->FIM Portal, the portal seems to accept the value.

Is there any way where we can configure FIM Portal to not accept Unsatisfactory inputs from other sources?

I am thinking its not possible to set this in FIM Portal and might be we have to manually be sure of the Owner value what we set using Powershell or AD.

Please let me know your thoughts on this.

Thanks!

May 7th, 2015 5:10am

You could add an MPR to check the values using e.g. Granfelts Lookup Value Workflow. Add your required parameters to the lookup, and then blank the value if it's invalid.

Of course, this will lead to problems when the value is flowed from AD --> MV --> FIM Portal, as the FIMSync Engine will try to set the value again. To solve this, you could use another attribute, and then always run the MPR/WF with the Lookup Value WF.


Free Windows Admin Tool Kit Click here and download it now
May 7th, 2015 5:32am

You could add an MPR to check the values using e.g. Granfelts Lookup Value Workflow. Add your required parameters to the lookup, and then blank the value if it's invalid.

Of course, this will lead to problems when the value is flowed from AD --> MV --> FIM Portal, as the FIMSync Engine will try to set the value again. To solve this, you could use another attribute, and then always run the MPR/WF with the Lookup Value WF.


May 7th, 2015 9:30am

You could add an MPR to check the values using e.g. Granfelts Lookup Value Workflow. Add your required parameters to the lookup, and then blank the value if it's invalid.

Of course, this will lead to problems when the value is flowed from AD --> MV --> FIM Portal, as the FIMSync Engine will try to set the value again. To solve this, you could use another attribute, and then always run the MPR/WF with the Lookup Value WF.


Free Windows Admin Tool Kit Click here and download it now
May 7th, 2015 9:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics