Job to enable all Users in Identity Store, solution for mass maintenance

[Former Member]

Hi all,

I user IDM 7.2 SPS3

Because IDM unfortunately have no user mass maintenance, I'm just trying to create one.

1. I create a job

2. In the source tab I use the entrytype MX_PERSON from my ID-Store. (So I get all User in the ID-Store)

3. In the destination tab I set for all users the attribute MX_DISABLED to value FALSE

When I run the job the following happens:

-The "MODIFY Script" from SAP Provisioning framework is triggered

-After that the Mark Disabled script starts and then the Exec Plugin Disable User script.

As a result, all user are disabled.

It does not matter what value I give to MX_DISABLED. I tried TRUE, FALESE; null, "", ", "FALSE", "TRUE"...

every time with the same result.

Does anyone have a solution for this problem? Or another solution?

[former_member2987 · Accepted solution]

Gerhard,

I believe it needs to be 1 or 0.

Matt

[Former Member · Accepted solution]

Hi Matt,

Thanks for your answer...

0 or 1 brings the same result.

The script which handles the value looks like this:

// Main function: sap_asj_handleBooleanJava

function sap_asj_handleBooleanJava(Par) {

var result = "";

if (Par == null || Par == '' || Par == "" || Par == "0" || Par == "false" || Par == "FALSE") {

result = false; // interpreted as Boolean-False

}

else

// if a value exists: interpreted as Boolean-True

{

result = true;

}

return result;

}

[former_member2987 · Accepted solution]

It could be in how the task is being called. Are you doing a reconciliation in IDM or does the enable happen as a part of a workflow?

[Former Member · Accepted solution]

Normally, the enable/disable processes can be triggered via UI for a single user. MX_DISABLED is a checkbox when it is selecting the User gets disabled, if you remove the hook from MX_DISABLED the user gets enabled.

But I do not want edit each user individually

[Former Member · Accepted solution]

Hi Gerhard,

I think MX_Disabled would run in the Same Way like Mx_inactiv runs. You hav to remove this attribute from the user using as value within your job. After that your users should be enbled.

Kind regards,

Achim Heinekamp