Supported SCIM Schemas
What Are SCIM Schemas?
In SCIM (System for Cross-domain Identity Management), schemas define the structure of resources such as Users and Groups. They specify what attributes exist (e.g. userName
, givenName
, email
), their data types, and whether they are required or optional.
Schemas are essential to ensure interoperability between Identity Providers (IdPs) and service providers like Fairjungle. Each resource (e.g. User) includes a reference to one or more schemas to indicate the data model it follows.
There are two types of schemas in SCIM:
- Standard Schemas, defined by the SCIM specification (RFC 7643)
- Custom (or Extension) Schemas, defined by the service provider to support domain-specific needs
Schemas Supported by Fairjungle
Fairjungle supports a subset of the SCIM 2.0 standard, focused primarily on user lifecycle management. The following core operations and schemas are implemented:
Standard SCIM Operations
- ✅ Create User (RFC 7644 §3.3)
- ✅ Retrieve User (RFC 7644 §3.4.1)
- ✅ List Users (RFC 7644 §3.4.2)
- ✅ Query Users with HTTP POST (RFC 7644 §3.4.3)
- ✅ Replace User (RFC 7644 §3.5.1)
- ✅ Patch User (RFC 7644 §3.5.2)
- ✅ Delete User (RFC 7644 §3.6)
Fairjungle adheres to the standard User schema as defined in RFC 7643 §4.1, including attributes like:
userName
name.givenName
name.familyName
emails
active
Fairjungle Custom SCIM Schema
In addition to the standard schema, Fairjungle also defines a custom extension schema to support business travel-specific data that is not part of the SCIM core. See Fairjungle SCIM Schema for more information.
Notes
- Fairjungle currently does not support SCIM Group operations (e.g., creating or patching groups).
- Group-based assignment can be achieved via your IdP and reflected in Fairjungle using mapped attributes like
department
ortravelPolicy
.
Related Resources
- SCIM Overview
- SCIM Setup Instructions
- Fairjungle-side custom field mapping API Reference
- User creation (RFC 7644 - 3.3)
- User retrieving (RFC 7644 - 3.4.1)
- Users querying (RFC 7644 - 3.4.2)
- Users querying with HTTP POST (RFC 7644 - 3.4.3)
- User replacement (RFC 7644 - 3.5.1)
- User patching (RFC 7644 - 3.5.2)
- User deletion (RFC 7644 - 3.6)