SCIM 2.0 (System for Cross-domain Identity Management) is an industry-standard protocol for automating user provisioning between identity providers and applications. By enabling SCIM in Flip, you can:
- Automatically create users in Flip from your identity provider
- Keep user profile information in sync
- Lock users in Flip when they are deactivated in your identity provider
Setup Steps
Step 1: Generate Token
- Admin Console → Access & Security → SCIM
- Enable SCIM
- Copy and securely store the token
- Copy the SCIM base URL
Step 2: Configure Identity Provider
For Entra ID:
Connect Entra via SCIM
- Create a custom Enterprise Application
- In the created Enterprise Application, click Provisioning
- Set Provisioning Mode to "Automatic"
- Enter the SCIM URL and Token under “Admin Credentials”
- Test the connection
- Click Save
Configure Attribute Mapping
- In the Enterprise Application under Provisioning, click Attribute Mapping (Users)
- Modify or remove specific mappings (Flip Attribute Mapping)
- Create additional attribute mappings
- Click "Show advanced options" and then "Edit attribute list for customappsso"
- Add the desired Flip SCIM Extension.
- Predefined attribute example (technical name
location):urn:ietf:params:scim:schemas:extension:flip:location:2.0:User:value
Note: use:valueand not.valueat the end. - Custom attribute example (technical name
soccer_team):urn:ietf:params:scim:schemas:extension:flip:custom:2.0:User:attributes[technicalName eq "soccer_team"].value
Note: use.valueand not:valueat the end.
- Predefined attribute example (technical name
-
Important: Custom Attributes during initial provisioning (Entra workaround)
Microsoft Entra does not reliably send complex attributes (e.g....:custom:2.0:User:attributes[...]) during the initial user creation (Microsoft Source). To address this limitation, Flip provides an additional JSON-based extension.
Schema URN:urn:ietf:params:scim:schemas:extension:flip:customJson:2.0:User:value
Important: The target attribute must end exactly with:value. If:valueis missing, the mapping will not work.
Steps:- Add the following attribute (Type: String) to the attribute list:
urn:ietf:params:scim:schemas:extension:flip:customJson:2.0:User:value - Create a new mapping with:
Mapping type: Expression
Target attribute:urn:ietf:params:scim:schemas:extension:flip:customJson:2.0:User:value
Example expression:Join( "", "{\"attributes\":[{\"technicalName\":\"custom_team\",\"value\":\"", [department], "\"},{\"technicalName\":\"custom_location\",\"value\":\"", [city], "\"}]}" )
The rendered result must look like:{"attributes":[{"technicalName":"custom_team","value":"Engineering"},{"technicalName":"custom_location","value":"Berlin"}]}
For subsequent updates, the standard custom extension (...:custom:2.0:User:attributes[...] .value) can continue to be used. - Add the following attribute (Type: String) to the attribute list:
- Click "Save"
- Click "Add New Mapping"
- Select the source and corresponding target attribute
- Click "Ok"
- Click "Save"
Select Users or Groups
- In the Enterprise Application under Provisioning, go to Users and Groups
- Click "Add user/group"
- Select the individual users or groups that should be provisioned
Start Provisioning
- In the Enterprise Application under Provisioning, go to Overview
- Click "Start provisioning"
For Okta:
Enable SCIM in the Okta App
- Create a new App Integration of type SAML 2.0.
- Configure SAML Single Sign-On (SSO) as described in this article:
SAML SSO Configuration in Flip - After successfully setting up SSO, go to the General tab.
- Under App Settings, click Edit.
- Under Provisioning, select SCIM and save the changes.
- A new tab called Provisioning will appear.
Configure SCIM Connection
- Open the Provisioning tab.
- Click Edit and enter the SCIM URL.
- For Unique identifier field for users, use:
userName - Enable the following options under Supported provisioning actions:
- Push New Users
- Push Profile Updates
- Set Authentication Mode to HTTP Header.
- Paste the SCIM Token into the Authorization field.
- Test the connection via Test API Credentials and save.
- In Provisioning → To App, enable the following actions:
- Create Users
- Update User Attributes
- Deactivate Users
Configure Attribute Mapping
- Navigate to Provisioning → To App → Attribute Mappings.
- Edit or remove existing attribute mappings (see Flip Attribute Mapping).
- To add custom attributes:
- Go to the Profile Editor.
- Click Add Attribute.
- Set a Display Name and Variable Name.
- Set the External Name to
value. - For External Namespace, use (see Flip SCIM Extensions), e.g.:
urn:ietf:params:scim:schemas:extension:flip:location:2.0:User - Click Save.
- The new attribute will now appear under Provisioning → To App → Attribute Mappings and can be mapped there.
Assign Users or Groups
- Go to the Assignments tab.
- Click Assign → Assign to People or Assign to Groups.
- Select the users or groups you want to provision.
Start Provisioning
- Go to Provisioning → To App again.
- Enable the following options:
- Create Users
- Update User Attributes
- Deactivate Users
- Make sure all required attributes are mapped correctly.
- Provisioning will automatically start for all assigned users and groups.
For OneLogin:
- Use “SCIM Provisioner (SCIM v2 Enterprise) - No Params”
- Enter SCIM JSON, URL & Token in the “Configuration” tab
- Map attributes in the “Parameters” tab
- Enable provisioning
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| 401 Unauthorized | Invalid token | Check token |
| 400 Missing userName | Missing mapping | Ensure correct attribute mapping |
| Attributes missing | Incorrect mapping | Compare mapping to schema table |
| User not created | Sync not triggered | Check assignment and logs |
Best Practices
- Start with a few test users
- Use
externalIdfor unique identification - Regularly check provisioning logs
- Plan and document attribute mappings early
- Document any custom attributes in use
If you run into issues, please contact Flip support and include:
- Your Flip Tenant ID
- Error messages and API request/response examples