Identity Governance & Administration
sara.next
  1. sara.next
  2. Integrations
  3. SQL auto-implementation

Integrations · Integration models

SQL auto-implementation

For databases and applications in which access can be safely managed at the database level — through queries, procedures or controlled permission tables.

  • level L4
  • SQL

Diagram

A change executed in the database

01 · sara.next

  • Auto-implementation queueapproved requests
  • Operation scriptscreate · change · delete · check

02 · Connection

  • Technical accountminimum scope of permissions
  • SQL or proceduresdefined operations

03 · Application database

  • Permission tablescontrolled write
  • Database rolesuser assignments

Caution

When not to use SQL

Writing directly to another application's database is often not supported by the vendor. In that case an adapter or the manual model is better.

Adapter and middleware

Warning signs

  • The vendor does not allow direct changes in the database
  • Permissions are spread across the application logic, not in tables
  • The effect of a change cannot be checked
  • No test environment

Configuration

SQL connection and scripts in brief

SQL connection and scripts in brief
ElementWhat it contains
SQL connectionName, system name, JDBC URL, user name and password.
Implementation scriptA Groovy script returns a single SQL statement or a list of statements executed in one transaction, rolled back on error.
Verification scriptA SELECT query; at least one row means the change is confirmed.

See sara.next on your own scenarios

During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.