AD Account Creation behavior

[AdrianMarchis]

Hello,

We encountered the following issue, I can create accounts with entitlements in AD and tasks get run when I run the job but I have noticed some behaviors I want clarified.

1. If I try to run a create account task without any associated entitlements the task doesn't get picked up at all by the job. It doesn't even attempt to run the task (no provisioning tries or anything no matter how many times we run the job). Why could this be? For context, we simply request an account from ARS without requesting any entitlement with it.

Here's a screenshot of the task after the provisioning job was run:

2. When doing the request with both account and entitlement, the tasks are run and both end up succeeding in the end system. However, only the add access task was immediately moved to complete. We see the typical success message (checking DN) in the new account task that still sits in pending tasks, but it doesn't move for a couple of minutes to complete even though it is, even after we import from AD for recon. Why is this happening? It eventually moves but even then in completed tasks, it says "No action required".

Here's a screenshot of the tasks after the provisioning job and import job were run:

Thank you!

[rushikeshvartak]

• Share logs in text file 
• Share WSRETRY job config

[AdrianMarchis]

After the request, I uploaded a CSV of the logs and a screenshot of the provisioning job.

[This message has been edited by moderator to mask sensitive information]

[rushikeshvartak]

Are you using entitlementsonly under security system ?

[AdrianMarchis]

Understood, will capture them and upload.

[AdrianMarchis]

@rushikeshvartak No, the setting is left empty.

[rushikeshvartak · Accepted solution]

Validated in 24.9 and its working