Fairjungle Schema

In addition to Core and Enterprise schemas, we provide a fairjungle schema with additional attributes.

info

Fairjungle Schema URI is urn:ietf:params:scim:schemas:extension:fairjungle:2.0:User

Attributes

SCIM urn:ietf:params:scim:schemas:extension:fairjungle:2.0:User	Fairjungle User	Read-Only	Note
billingProfile.id	billingProfileId
billingProfile.name		✅
costCenter.id	costCenterId
costCenter.name		✅
dateOfBirth	dateOfBirth		Format: YYYY-MM-DD
gender	gender		Values: female or male
manager.id	managerId
manager.email		✅
roles[].display		✅
roles[].value	roles		Values: accountant, admin, authAdmin, guest, guestCreator, manager, organizer and premium
travelPolicy.id	travelPolicyId
travelPolicy.name		✅

Resolving

Billing Profile

When creating, replacing or patching user, the billing profile must already exist on fairjungle:

• if only billingProfile.id is provided, then billing profile is found by id
• if only billingProfile.name is provided, then only one billing profile must already exist with this unambiguous name
• if both billingProfile.id and billingProfile.name are provided, then billing profile is found by id and a check is performed to verify that name is the same

Cost Center

When creating, replacing or patching user, the cost center must already exist on fairjungle:

• if only costCenter.id is provided, then cost center is found by id
• if only costCenter.name is provided, then only one cost center must already exist with this unambiguous name
• if both costCenter.id and costCenter.name are provided, then cost center is found by id and a check is performed to verify that name is the same

Manager

When creating, replacing or patching user, the manager must already exist on fairjungle:

• if only manager.id is provided, then manager is found by id
• if only manager.email is provided, then manager is found by email
• if both manager.id and manager.email are provided, then manager is found by id and a check is performed to verify that email is the same

Travel Policy

When creating, replacing or patching user, the travel policy must already exist on fairjungle:

• if only travelPolicy.id is provided, then travel policy is found by id
• if only travelPolicy.name is provided, then only one travel policy must already exist with this unambiguous name
• if both travelPolicy.id and travelPolicy.name are provided, then travel policy is found by id and a check is performed to verify that name is the same

User Replacement

When client issues a User Replacement and urn:ietf:params:scim:schemas:extension:fairjungle:2.0:User attribute is NOT present in request content, then attributes are NOT removed from fairjungle user.

warning

This is an exception to the rule "Attributes not provided in request are removed" when replacing a user.