AD Blocker will try for 60 minutes to block/unblock users not found in the AD and log it (#21171 #21287)

Figure 1 - Notification that user was not found in the AD

Cause

This could occur when there were users mapped in the system and the AD Blocker was not able to block or unblock them.

• The majority of cases happen due to typo mistakes
• When the users were already blocked this issue could also be experienced 

This could cause a timeout request issue when users were requesting to be unblocked.

Prevent Future Issues

To prevent futures issues and to help teams to solve it in a faster way:

• The AD Log will be logging the AD Username that was not found
• The system will only try for 60 minutes after the blocking/unblocking process for any issue that could happen when the task was running
• If the user is already blocked in the AD, it will be synced
• This will fix the request unblocked timeout

Configurations

AD Blocker version

• V1.0.3 - https://github.com/SkillsWorkflow/ADBlocker/releases/tag/v1.0.3

To a user be blocked it is necessary to:

• The user is Active
• "Timesheets Required" is checked
• Must have a valid AD User Name
• The company must have Lock Timesheet Type Daily/Weekly
• The user must have a Minimum Daily/Weekly Hours
• The user cannot have the "Administrator" role

Proposed Tests

1. Create a new user in the system
2. Setup the user with an AD username that does not exist in the AD
3. Wait until the AD blocking task run
4. Verify that the AD username not found was logged

Historical Data

There were no needs to rectify the historical data since the AD Blocker is running all the day.

• Every time the AD Blocker runs is verified if there were users to blocked that were not successfully blocked
• If the user is already blocked in the AD, it will be synced
• When the user is not correctly mapped, it will be marked as not found in the log