license agent's schema mapping failed on the new SCIM vendor endpoint
Fixes license agents whose SCIM schema mapping breaks on a new vendor endpoint. Use when the mapping fails after switching vendors. Not for PATCH violations.
TL;DR
Re-read the new vendor's schema from its Schemas endpoint and rebuild the mapping. Every vendor's SCIM schema differs, and mappings do not transfer.
Error
(schema mapping failed on the new SCIM vendor endpoint; attributes unmapped; no error text)Steps
- Fetch the new vendor's schema from its Schemas endpoint. Expected: the actual supported attributes in hand.
- Diff it against the old vendor's schema to find renamed, missing, and added attributes. Expected: the differences listed.
- Rebuild the agent's attribute mapping against the new schema, dropping or remapping what the new vendor lacks. Expected: a vendor-correct mapping.
- Test provisioning reads and writes against the new endpoint. Expected: the mapping works.
When to use
- The SCIM vendor changed and the mapping broke
- Attributes that mapped before are now unmapped
- The new endpoint behaves differently
When not to use
- The vendor is the same but PATCH fails (a PATCH construction problem)
- Auth fails before any schema is read (a credential problem)
- The mapping is right but data is wrong (a data problem)
Tool compatibility
SCIM 2.0 vendor endpoints.
Variant phrasings
vendor documents the schema but the endpoint differs
Trust the endpoint; documentation lags.
mapping works for users but not groups
Groups have their own schema. Map them separately.
Why it happens
SCIM is a framework, not a fixed schema. Vendors extend and restrict it freely, so any mapping is vendor-specific by construction.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_lH5yh89V7wwqB20G5lPZOA