# SCIM (Beta)

# Preamble

The EE server support user and group management with SCIM, in combination with SAML. SCIM allows external services to create / delete / update users and groups. Psono doesn't implement the full SCIM specification and instead currently supports the subset required by Azure. This guide here will explain how to configure SCIM. We assume that your webclient is running on https://example.com, the server is reachable with https://example.com/server (e.g. https://example.com/server/info/ shows you some nice json output).


This feature is only available in the Enterprise Edition.

# Enable SCIM

Lookup the provider id of your SAML configuration. If your configuration looks like this:

            entityId: ...

Then your provider id is 1. So create a SCIM configuration that looks like this:

        TOKEN: 'Replace me with a secure long random string'
        PROVIDER_ID: 1
  • Change TOKEN parameter and replace it with a secure random string. This will later be used by the SCIM provider as authentication.
  • Change PROVIDER_ID parameter to match your SAML configuration's provider id
  • Change AUTOPROVISION_PSONO_GROUP parameter and set it to true, if you want that Psono automatically creates a corresponding Psono group for any new SCIM group and an appropriate group mapping.
  • Change AUTOPROVISION_PSONO_FOLDER parameter and set it to true, if you want that Psono automatically creates a folder with the same name as the group and shares it with the automatically created Psono Group. (Requires AUTOPROVISION_PSONO_GROUP to be set to true to have any effect.)

Restart the server afterward.

The SCIM endpoint is now: https://example.com/server/scim/2.0/1, so e.g.

  • https://example.com/server/scim/2.0/1/Schema
  • https://example.com/server/scim/2.0/1/Users
  • https://example.com/server/scim/2.0/1/Groups

Users and groups should now automatically be provisioned.