Scheduling infrastructure for absolutely everyone.
- To be moved to proper documentation location
- When a user is assigned to the integration in Okta, they are created in Cal.diy with appropriate attributes.
- Only attributes that are defined in Cal.diy are synced.
- Attributes are mapped by label, i.e., the external variable name of the custom attribute in Okta must match the label of the attribute in Cal.diy (in a case-insensitive manner).
- Only two types of custom attributes are currently supported (Number type support is pending):
- string
- array of strings
- If an Okta custom attribute maps to a Multi-Select or Single-Select attribute in Cal.diy, the provided values must be among the options defined for that attribute in Cal.diy.
- Options are matched by label in a case-insensitive manner, similar to attribute labels
- Any option not defined on the attribute is ignored and not synced
- If the attribute is locked in Cal.diy, sync from Okta completely overrides the attribute's value for that user in Cal.diy. Okta serves as the source of truth in this case.
- After sync, no values will remain in Cal.diy for that user's custom attribute unless they are defined in Okta.
- If the attribute is not locked in Cal.diy, the expectation is that the attribute is marked as 'Create Only' in Okta and shouldn't be synced back to Cal.diy, after user's creation.
- But in case if the attribute is still synced back to Cal.diy, we handle it in following way:
- We consider two pools of assignments for the attribute:
- Directory Sync Pool: Assignments created by Directory Sync
- Cal.diy Pool: Assignments created by via Cal.diy
- A sync from Okta, would ensure that all assignments from Directory Sync Pool are removed and only those remain that are provided by Okta.
- Any update in Cal.diy is restricted to assignments in Cal.diy Pool only and doesn't impact Directory Sync Pool.
- In case an option already in Cal.diy pool is assigned to a user through Directory sync, the ownership for that assignment is transferred to Directory Sync and it moves to Directory Sync Pool.
- We consider two pools of assignments for the attribute:
- But in case if the attribute is still synced back to Cal.diy, we handle it in following way: