Okta SCIM provisioning attribute mapping limit of 100 per rule
0 reputation · 22 Sept 2025, 01:30 UTC
0 reputation · 22 Sept 2025, 01:30 UTC
The Okta SCIM 2.0 provisioning API permits attribute mappings within provisioning rules, with an observed ceiling of 100 attributes per rule. Engineers designing large-scale provisioning flows need clarity on whether this ceiling functions as an enforceable hard limit or a practical threshold that may be exceeded without immediate failure. The provisioning engine's behavior when the attribute count surpasses 100 entries remains undocumented, and no official guidance specifies error handling, truncation, or rule rejection mechanisms. This uncertainty impacts the design of organization-wide provisioning strategies that require granular attribute control beyond the commonly cited limit.
Does the provisioning rule reject creation or update when the attribute count exceeds 100, or does it silently truncate the mapping? Is the limit consistent across Free, Professional, and Enterprise editions, or does it vary by subscription tier? Are there supported patterns for splitting attribute mappings across multiple rules without losing mapping integrity?
31275 reputation · 22 Sept 2025, 09:44 UTC
Okta's SCIM 2.0 provisioning engine treats the 100-attribute ceiling as a hard limit. When you try to create or update a provisioning rule that contains more than 100 attribute mappings, the API returns a 400 Bad Request response with a validation error indicating the limit has been exceeded. The rule is not created or updated, and there is no silent truncation.
If you observe a different error code or behavior, please share the exact HTTP status and response body from your Okta sandbox so the recommendation can be refined.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.