Sovrain
  1. Documentation
  2. Identity provider

Explanation

Provisioning accounts in applications

Why Sovrain pushes accounts to applications over SCIM, why changes wait before they are sent, and why the regular check never deletes anything.

Single sign-on answers who may sign in. It does not create the person’s account inside the application, keep their name and email up to date there, or switch the account off when they leave. Many applications need an account to exist before the first sign-in, for example to assign work to someone who has never logged in. Provisioning closes that gap: Sovrain creates, updates and removes accounts in the application for you, using the SCIM 2.0 standard.

Sovrain pushes, the application listens

SCIM has two sides. A SCIM server holds accounts and accepts changes; a SCIM client sends them. Sovrain is only a client. It connects to the application’s SCIM address with a token the application gave you, and sends it users and groups. Nothing connects to Sovrain over SCIM to read or write accounts.

The direction says where the truth lives. People are created, renamed and removed in Sovrain, and every connected application follows. The flip side is that Sovrain cannot be fed from somewhere else: an HR system or another directory cannot create accounts in Sovrain over SCIM. If people come from another system, they come in through invitations or the Admin API.

Who is sent, and who may sign in

Each SCIM connection has its own scope: either everyone in the organization, or selected groups and individual people. New connections start with nobody selected, so turning provisioning on sends nothing until you say whom to send.

The scope is separate from the groups that may sign in. Usually the two match, but they do not have to. You might provision a whole department so that colleagues can mention each other, while only some of them may sign in yet. Or an application might be sign-in only, with no provisioning at all. People who are invited but have not accepted are never sent, even if they are already in a group in the scope; they are sent once they join.

Why changes wait

When you change something that affects an application, such as removing Bob from a group in its scope, Sovrain does not call the application at that instant. It works out the difference between what the application should contain and what it has been sent, queues the needed changes, and holds each one for three minutes before sending it.

That short wait is a safety margin. Group changes are easy to get wrong, and the effect of a wrong one in an application can be hard to undo: a deleted account may take its data with it. During the wait you can see the queued change and cancel it. A cancel is a pause of 5 minutes, not a veto: unless you change what caused it, the change comes back. The wait also lets a series of quick edits settle into what you actually meant before anything leaves Sovrain.

For bigger changes, Sovrain shows the impact before anything is queued. Saving a new scope or a new attribute mapping first shows how many accounts would be created, updated or removed, and asks you to apply it. When you change the members of a group, the group page warns you which provisioned applications are affected and how many accounts would be deactivated or deleted.

When an application fails to answer or reports a temporary error, Sovrain retries with growing pauses, from 30 seconds up to a day; a request the application rejects as invalid is not retried, and the job is shown as failed. It respects an application that asks it to slow down. If the application rejects the token outright, Sovrain pauses the whole connection rather than repeating the same failure, and resumes only after a connection test passes again.

The regular check never deletes

Every six hours, Sovrain reads all users and groups the application has and compares them with what it believes it sent. This catches changes made behind its back. It links accounts that match by user name, takes over matching accounts that already existed in the application, re-creates groups it made that have gone missing, and switches back on accounts that someone switched off directly in the application. If Sovrain says an account should be active, it will be.

What the check never does is remove anything. Applications often hold accounts that Sovrain did not create and should not touch: a local admin account, a service account, people from before Sovrain was connected. A check that deleted every account it does not recognise would be one misconfiguration away from wiping an application. So the check only records these accounts as drift and shows them to you.

Removing drift is a separate, deliberate act. You can remove single entries, or choose Force sync…, which removes every drifted account the way the connection removes people (deactivated by default, or deleted, following the Deprovisioning behavior) and deletes every group Sovrain does not track in the application. Force sync removes them even when Deactivate users is turned off. It exists for the moment you really want the application to match Sovrain exactly, and it asks for confirmation because it cannot be undone from Sovrain’s side.

Ordinary removals are different from drift. When someone leaves the scope, is suspended or is removed in Sovrain, the regular sync removes them from the application as configured, without waiting for a force sync.

Deactivate or delete

When a person should no longer be in an application, Sovrain can either deactivate the account, by setting it inactive, or delete it. Deactivation is the default, and it is usually the safer choice. The account stops working, but the application keeps everything attached to it: documents they own, history that names them, assignments. If the person comes back, or was removed by mistake, the account can simply be made active again.

Deleting frees the account completely, which some applications need, for example to release a paid seat. The price is that whatever the application deletes with the account is gone. Sovrain also lets you switch removal off altogether: with Deactivate users turned off, the regular sync neither deactivates nor deletes anyone (Force sync still does), and leaving accounts behind becomes your decision.

Two more cases do not remove anyone. Disabling the application in Sovrain stops synchronising but leaves accounts as they are, and removing the SCIM connection does not undo the accounts it created.