Scheduler Based Provisioning

This document will walk you through the steps required to configure Scheduler Based Provisioning. It will also guide you through the steps required to perform CRUD operations during Scheduler Based Provisioning.

What is Scheduler-Based Provisioning?

Scheduler-based provisioning refers to a method of provisioning users where user sync occurs at specific intervals of time or when CRON runs. This involves queuing CRUD operations performed on a Drupal site and executing them on the SCIM server application when the scheduled interval has passed or when CRON operations are carried out. 

The User Provisioning module facilitates User Management between your Drupal site and SCIM server applications specifically Create, Update, and Delete operations.

How to set up Scheduler-Based Provisioning?

Prerequisite:  Download and configure the miniOrange User Provisioning module with your SCIM Server.

• Once you are done configuring the module with the SCIM server application and Attribute mapping, click on the Next Step button in the Attribute Mapping section under the User Provisioning tab of the module.
• From Choose when to trigger User Sync & Provisioning, enable the Scheduler-Based Provisioning checkbox.
• From the Provisioning Operation section, select the Operations - Create, Read, Update, Delete, and Deactivate that you want to enable during Scheduler-Based Provisioning.
• After selecting the operations, click on All Done! button.

The operations to be performed during Scheduler Based Provisioning:

Read User:

The Read User feature works whenever a request is sent from the Drupal site to the SCIM server application. Whenever any Create, Update, or Delete/Deactivate operations are performed from the Drupal site, the Read operation is performed first to check if the user exists in the SCIM server application.

Create User:

When a new user is registered on the Drupal site and gets provisioned to the SCIM server application, a corresponding user account is created on the SCIM server application with the provisioned user information.

• Once you are done with the configuration steps, create a new user account on the Drupal site.
• The new user created is added to the queue and once the Scheduled time is elapsed or CRON operations are executed, the user gets provisioned to the SCIM server application.
• Once the CRON runs, you can navigate to the SCIM server application to check if the user is created by searching for the user in the user section.

Let’s see how Create User works:

Let us assume you create a new user (testuser01@gmail.com) on the Drupal site.

Once the user is created at the Drupal site, and the Scheduled time is elapsed or the CRON operations are completed, navigate to the Users section of the SCIM server application and search for the user provisioned.

Update user:

Any updates made to a user's information on the Drupal site are synced with the SCIM server application either after a scheduled time interval or when the CRON operation is triggered.

• Once you are done with the configuration steps, update the user information on the Drupal site.
• The update user operation is added to the queue, and once the Scheduled time has elapsed or CRON operations are executed, the user gets provisioned and the user information gets updated at the SCIM server application.
• Navigate to the SCIM server application, you can check if the user is created by searching for the user in the user section.

Let’s see how the Update user works:

Let us assume you update a user (testuser01@gmail.com) on the Drupal site.

Once the user is updated at the Drupal site and the Scheduled time is elapsed or the CRON operations are completed, navigate to the Users section of the SCIM server application and search for the user provisioned.

Deactivate user:

If the status of a user is changed to "blocked" or "deactivated" on the Drupal site, the same change in status will be reflected on the SCIM server application. However, this will only occur once the CRON operation or Scheduled time interval is complete.

Note: During the configuration steps, make sure that the Deactivate user checkbox is enabled under Provisioning Operations. You can confirm this by clicking on the Edit button to verify your configurations.

• Once you are done with the configuration steps, search for the user in the People tab and deactivate or block the user.
• After the user has been deactivated, the operation is added to a queue.
•  Whenever the CRON operations are performed or the scheduled time has elapsed, the user gets provisioned to the SCIM server application.
• Navigate to the SCIM server application, you can check the user’s status by searching for the user in the user section.

Let’s see how Deactivate user works:

Let us assume you want to deactivate a user(testuser01@gmail.com) in both the Drupal site as well as the SCIM server application.

Once the user is deactivated at the Drupal site, and the Scheduled time is elapsed or the CRON operations are completed, navigate to the Users section of the SCIM server application and search for the user provisioned.

Delete user:

If a user is deleted from the Drupal site, the corresponding user in the SCIM server application will also be deleted, either after the scheduled time interval is completed or after the CRON operations are finished.

• Once you are done with the configuration steps, search for the user in the People tab and delete the user.
• After the user has been deleted from the Drupal site, the operation is added to a queue.
•  Whenever the CRON operations are performed or the scheduled time has elapsed, the user gets provisioned to the SCIM server application.
• Navigate to the SCIM server application, you can confirm if the user is deleted or not by searching for the user in the user section.

Let’s see how Delete user works:

Let us assume you want to delete a user(testuser01@gmail.com) in both the Drupal site as well as the SCIM server application.

Once the user is deleted from the Drupal site, and the Scheduled time has elapsed or the CRON operations are completed, navigate to the Users section of the SCIM server application and search for the user provisioned.

 Back to top