/ SONDA · ENTERPRISE

Your identity provider, with nobody in between.

Single sign-on through OpenID Connect or SAML 2.0, provisioning through SCIM 2.0, and directory sync from Entra ID or Okta — each one talking to your provider from your own side. There is no LockFlare server in the loop, because there is no LockFlare server.

OIDC SAML 2.0 SCIM 2.0 ENTRA ID · OKTA · GOOGLE

At a glance

OIDCA public client with PKCE on a loopback redirect. ID tokens with RS256, RS384, RS512, ES256 and ES384 verified. The scope and the email claim configurable.
SAMLMetadata import, HTTP-Redirect, single logout both ways, signed authentication requests with a team key, encrypted assertions, SP metadata exported.
RulesAllowed email domains. An offline grace of eight hours when the provider cannot be reached. A Try mode that shows every attribute the provider sends. The owner is exempt.
SCIMUsers and Groups, Entra-style PATCH, a group name mapped to a preset. Runs on your server with a provisioning key the owner issues per division.
DirectoriesEntra ID through Graph, Okta through its API: one group into one division, every fifteen minutes.
/ NOBODY IN BETWEEN

Sign-in goes to your provider. Provisioning runs on your server.

Each person's Sonda signs in straight at your provider — OpenID Connect as a public client with PKCE on a loopback redirect, or SAML 2.0. Provisioning is a SCIM 2.0 bridge on a server of yours, with a provisioning key the owner issues per division. Directory sync reads Entra ID through Graph and Okta through its API: one group into one division, every fifteen minutes.

Beside it, one person joining and one leaving — and the place a LockFlare server would sit, empty.

Sonda Server
/ PROVISIONING

A bridge that never makes keys.

A provisioned person still holds a key nobody else made. The bridge opens the door; it does not hold the key.

It joins someone the way anyone joins.

The provider creates the user through SCIM. The join request comes from the person's own Sonda, with the person's own key slot. The bridge approves it — checking every minute that the address is active at the provider, the invitation is current, and SSO has been passed if required.

It pauses. An administrator revokes.

A person removed at the provider is paused, not deleted; an administrator revokes in Sonda, which turns the keys of every project that person could read. A directory sync pauses people in no group and reactivates those put back.

It holds the lines it is given.

The seat cap of the license. Revocable provisioning keys that a Sonda Server also refuses once revoked.

/ THE REPORT

Every sync says what it did.

A directory sync reads the group, sets it against the division and writes down five lists — approved, reactivated, deactivated, awaiting and unmanaged — mailed if you like. People in no group are paused, not deleted; people put back are reactivated.

Beside it, one quarter-hour of one division. A directory that cannot be read removes nobody.

# directory sync · Platform · Entra ID group "platform-engineers" # every fifteen minutes · 08:15 approved 2 lu@example.com, mo@example.com # in the group, request waiting reactivated 1 jo@example.com # put back in the group deactivated 1 ex@example.com # in no group: paused, not deleted awaiting 3 in the group, no request yet unmanaged 4 left alone # a directory that cannot be read removes nobody mailed when a sync moved someone or failed
/ LOCKFLARE SONDA

SSO and SCIM, in the free edition.

Organizations and divisions, listed →