Identity Governance & Administration
sara.next
  1. sara.next
  2. Technology
  3. Auto-implementation configuration

Technology · Documentation

Auto-implementation configuration

Auto-implementation lets sara.next automatically make an access change — creation, modification or removal — in the target system once a request is approved, without manual intervention.

  • guide
  • Groovy
  • SQL
  • REST

Mechanism

How it works

The scheduler checks the queue every minute. This is how often the mechanism runs, not a guarantee of the time to make a change.

  1. Queue

    When an access request completes the approval process, it goes into the auto-implementation queue.

  2. Scheduler

    The scheduler runs every minute and processes requests from the queue.

  3. Script

    For each request the appropriate Groovy script is selected and executed on the configured SQL or REST connection. An optional verification script confirms that the change has been applied.

  4. Result

    The workflow receives "Implemented" or "Not implemented" — in the latter case with an error message.

Prerequisites

The connection first

Before you configure the scripts, define the connection they will use.

The connection first
ConnectionWhere in the panelFields
SQLAdministration → Configuration → SQL ConnectionsName, system name, JDBC URL, user name, password
RESTAdministration → Configuration → REST ConnectionsName, system name, base URL, authentication type (None / Basic / Bearer / API Key), credentials

The names of menu items, fields and buttons are given as they appear in the English version of the interface.

Configuration

Step-by-step configuration

  1. Open the application configuration

    Go to Administration → Applications and in the Actions column click the "Auto-implement config" button next to the chosen application.

  2. Enable the mechanism

    Tick the Enabled box.

  3. Choose the type

    In the Type field choose SQL or REST.

  4. Select the connection

    Choose the connection matching the type: SQL Connection or REST Connection.

  5. Fill in the scripts

    Fill in the script fields: Create, Replace, Modify, Delete and Verification.

  6. Save

    Click Save.

Variables

Variables available in scripts

All scripts receive the following variables.

Variables available in scripts
VariableTypeAlways availableDescription
userUserYesThe target user: the new user for Create and Modify, the user being swapped in for Replace. Properties: samAccountName, mail, givenName, surname.
oldUserUserNo *The previous user — available for Delete and Replace. In Delete scripts always use oldUser, not user.
roleRoleYesThe role being granted or revoked. Properties: id, name.
dimensionsMap<String, String>YesThe dimension values of the current request, indexed by system name, e.g. dimensions["DB_NAME"].
requestAccessRequestYesThe access request. In Delete and Modify scripts you can read the previous dimension values via request.oldAtar?.dimensionValues.
applicationApplicationYesThe configured application.
loginStringNo *Set only in the verification script. Contains the login to check: the new user for Create, Modify and Replace, the previous one for Delete.

* oldUser and login do not occur in all script types — see the table of script types for details.

Script types

Five scripts and their tasks

Five scripts and their tasks
ScriptWhen it runsAvailable variablesNotes
CreateWhen new access is granted.user, role, dimensions, request, application—
ReplaceWhen existing access is replaced (a different user or different dimensions).user, oldUser, role, dimensions, request, applicationIf the script is empty, the system runs Delete → Create in sequence.
ModifyWhen existing access is modified (the same user, changed dimensions).user, oldUser, role, dimensions, request, applicationAn empty Modify script is also replaced by the Delete → Create sequence.
DeleteWhen access is revoked.oldUser, role, dimensions, request, applicationTake the login of the access being revoked from oldUser, and the previous dimension values from request.oldAtar?.dimensionValues.
VerificationAfter the implementation script, to confirm that the change was made.as above, plus loginThe result is interpreted depending on the request type.

The Delete → Create fallback may mean a brief loss of access. For critical systems it is worth preparing dedicated Modify and Replace scripts.

Verification

Verification logic by request type

The verification script runs after the implementation script and confirms that the change has been applied. It has access to the login variable: for Create, Modify and Replace this is the new user, for Delete — the previous one.

Verification logic by request type
Request typeExpected verification result
Createtrue — the user exists in the target system
Modifytrue — the new state exists in the target system
Replacetrue for the new user and false for the previous one
Deletefalse — the user no longer exists (inverted logic)

Inversion for Delete: the scheduler inverts the result itself. The script is written as if it were checking for presence — verification passes when the user is not found.

Configure auto-implementation with our team

We will walk through the connection, scripts and verification using your application as an example.