Skip to Content
0

SAP IDM 7.2 task not being called during provisioning

Feb 01, 2017 at 09:23 PM

221

avatar image

When I provision a new user in IDM one of the tasks that assigns an active directory group to an active directory user is not being called. It calls the other AD tasks but not the one that assigns the group - Any ideas?? I.e. it calls CreatADSUser, Enable ADSUser, CreateExchange2010User, SetADSPassword but does not call AssignUserToADSGroup.

I cannot find out why and there are no errors I can find in any log.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Matt Pollicove
Feb 01, 2017 at 09:57 PM
0

Well, I guess I'd go with the basics, are the tasks enabled, and dispatchers assigned? Repository assigned? Can you run the workflow / task using test provisioning task?

Show 1 Share
10 |10000 characters needed characters left characters exceeded

I have narrowed it down even more. There is a Pass: 4. Exec Plugin - Assign User Membership task that runs. It runs for the ERP repository but it doesn't run for the AD repository.

0
Morley Freake Feb 01, 2017 at 11:17 PM
0

I have narrowed it down even more. There is a Pass: 4. Exec Plugin - Assign User Membership task that runs. It runs for the ERP repository but it doesn't run for the AD repository.

Show 7 Share
10 |10000 characters needed characters left characters exceeded

Is the task added in the hook task of the AD repository?

0

The task 4. Exec Plugin - Assign User Membership - is supposed to call the hook 4 task from each repository. It gets the one for the ERP repository but does not get the hook4 task for the AD repository.

0

Yes, so did you check the AD repository to see, if the constant for hook task 4 is maybe empty?

0

Yes, I did and it is as it should be. Here are the hook tasks for both but the issue is that after task 4. Exec Plugin - Assign User Membership runs for ERP it doesn't run for AD. It should run right after.

abap.jpg (23.9 kB)
ad.jpg (25.3 kB)
0

Hello Morley,

Assign User Membership to BS ABAP task belongs to "ABAP BusinessSuite Connector" while Assign User Membership to AD Group task belongs to "AD Connector" folder. These two are completely different tasks and uses the different passes (prior use To Custom pass while later uses To LDAP pass) also.

As your Assign User Membership to AD Group task is already linked to your repository and not getting triggered, please check the following points.

  1. Whether the task Assign User Membership to AD Group is Enabled?
  2. Whether a running dispatcher is assigned to this task?

If you find both the things fine then there could be the linkage issue so try to remove the job from hook task 4 in your AD repository and then add it again.

Regards,

C Kumar

1

I have verified everything and removed the job from the hook task and added it again and it is still not working. Any other ideas?

0
Show more comments
Deva Prakash B Feb 06, 2017 at 02:35 PM
0

Hi Morley,

As suggested by every one. Please check the following

1. Are there any wait tasks in Provisioning Queue search based on user mskey.(mxpv_provision).

2. Check the hook task in the respective repository.

3. check whether dispatchers are set & are running, whether action task and job is enabled for the task AssignUserToADSGroup under the AD Connector.

4. enable trace for the user and check the logs in the table or from admin ui.

Still issues then please drop me your lync or skype id to my message will contact you.

Regards,

DP

Share
10 |10000 characters needed characters left characters exceeded