Users created and removed automatically Groups and permissions from your identity platform One standard for all customers

Custom SCIM integration development

Appfront builds SCIM integrations: the open standard that lets identity platforms automatically create, update and remove users and groups in other applications. For organisations, that means new employees get access automatically, and leavers lose it on time. For software vendors, it means your application talks to every customer's identity platform in the same way. We build the SCIM side of your application, or the integration with an application that cannot do it yet.

What is a SCIM integration?

SCIM, System for Cross-domain Identity Management, is an open standard for automatically managing users and groups between systems. Via SCIM, an identity platform, such as an employer's, tells an application who should get an account, which details change, which groups someone belongs to, and who needs to be deactivated. Many identity platforms and business applications support SCIM.

An application without SCIM is maintained by hand: an administrator creates accounts and forgets to remove them when someone leaves. For a software vendor, this means every business customer asks how users can be managed automatically, and every answer is custom work. Larger customers often make it a procurement requirement.

We build it custom because applications differ: in how users, roles and permissions are structured, in which identity platforms your customers or your organisation use, and in how groups should be translated into permissions. The standard is fixed; we make sure your application works with it and has been tested with the platforms that matter.

Automatically on and off

Users created, updated and deactivated from the identity platform, with no administrator needed.

Groups become permissions

Groups from the identity platform translated into roles and permissions in your application.

One standard for everyone

One SCIM interface that every customer with a supported platform can connect to.

How we build your SCIM integration

We start with your application: how are users and permissions structured, which platforms need to connect, and how does it work today. Often, users are currently invited by email or created by an administrator at the customer. That route stays in place for customers without SCIM, so the integration never shuts anyone out.

1
Mapping your application and platforms

Your user model, roles, permissions and the identity platforms that matter.

2
Building the SCIM interface

Users and groups according to the standard, with security and mapping to permissions.

3
Testing with platforms

Testing with your customers' or your organisation's identity platforms.

4
Go-live and maintenance

Customer documentation, a log per action, and maintenance through updates.

What a SCIM integration actually does

The components below appear in almost every SCIM integration. Which ones you need depends on your application.

Users

Create, update, deactivate and delete.

Groups

Groups and memberships from the identity platform.

Permissions

Groups mapped to roles and permissions.

Security

Access to the interface using tokens per customer.

Testing

Tested with the most common identity platforms.

Log

What was done per action, and by which platform.

Who we build a SCIM integration for

The integration is intended for anyone who wants users managed automatically.

Software suppliers

Business customers who ask for SCIM. A single interface is the core.

Organisations with their own apps

In-house applications alongside off-the-shelf packages. Automatic deprovisioning on departure matters most.

IT departments

Applications without SCIM. An integration in between is what you need.

Platforms with many customers

Many environments per customer. Separation per customer is the core.

Technology and integrations

This page is about SCIM integrations. For a Tools4ever identity platform, see our page on a HelloID integration; for Microsoft, our page on an Azure AD integration; and for custom identity and access management, our page on an IAM system. You can read about our way of working on building custom software.

SCIM Users Groups Roles and permissions Deactivation on departure Tokens per customer Identity platforms Tests per platform Customer documentation Log per action

Why Appfront for your SCIM integration?

An account that survives after someone leaves is a risk, and a customer who walks away because of it is lost revenue. That is what we build on: users who are switched on and off automatically, permissions derived from groups, and one standard for everyone.

No manual work

Administrators no longer need to keep accounts up to date.

Secure on departure

Anyone who leaves loses access immediately.

Procurement requirement met

Customers who ask for SCIM can connect.

Security and privacy in a SCIM integration

The SCIM interface controls who has access to your application. It is secured with tokens per customer or environment, only grants access to user management, and every action is logged.

The integration runs in your application's environment, with encrypted connections and storage, and daily backups.

Frequently asked questions about a SCIM integration

Questions that software vendors and IT departments ask before getting started.

System for Cross-domain Identity Management is an open standard for automatically managing users and groups between systems. Via SCIM, an identity platform sends who should get an account, what changes, and who should be deactivated.

Because they don't want to manage users by hand in every application, and because an account that survives after someone leaves is a risk. For many larger customers it is a procurement requirement.

For each customer or environment, you define which group from the identity platform gets which role in your application. If someone's group changes, their permissions change with it. A customer can manage this mapping themselves in your application's settings, so your own support team isn't needed.

With the platforms that support SCIM. Because they don't all use the standard in exactly the same way, we test with the platforms that matter to your customers or your organisation.

The identity platform sends a deactivation, and the user loses access immediately. Whether the account is then deleted or retained is something you define, for example because data belonging to that user is still needed. Every creation, change and deactivation is logged, so a customer can see during an audit who had access and when.

Yes, with an integration that speaks SCIM on one side and the application's interface on the other. That way, even an application without SCIM can be managed automatically.

Software vendors with business customers who require automated user management, and organisations with in-house applications that need to be connected to their identity platform.

Users who switch on and off automatically?

Tell us how users and permissions are structured in your application and which identity platforms need to connect. We'll show you what the integration looks like.

Edit content