Activate a field mapping version.
curl --request POST \ --url https://auth.example.com/api/admin/field-mapping/field-mapping-sets/example/versions/example/activate \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "snapshotId": "mapping_snapshot_123", "activationScope": { "clients": [ "web-app" ] } }'Activates a compiled field mapping version for the supplied activation scope. Requires a compiled snapshot id in the request body. A set the platform owns applies to every tenant, so its activation is stored with an empty scope (a tenant-wide scope is accepted and normalised; a narrower one is refused), and it must release into exactly one OIDC Destination Profile that the platform owns. While the set has a version in use and is named by a default, an app, a SAML provider, a credential profile or SCIM, the version put in its place must still release into exactly one active Destination Profile of the kind in use (and, for a platform set, hold only what a platform set may), keep the version or snapshot that an app, a SAML provider or a credential profile is bound to, and the scope of the new activation must still apply to the context of each of them; otherwise 409 with reason would_break_references and the failed condition in references.violation. Mappings that read what comes in (SAML identity providers, SCIM) and credential mappings need no Destination Profile. The profiles counted are the ones the runtime counts: those the version’s edges name together with the destinationProfileId of the activation scope. A SAML provider’s saved release policy and attribute names must still hold for the new version’s profile, by the rules that save the provider’s configuration. When more references exist than are read in full, the change is refused as scan_incomplete; the list in references is then a lower bound (countIsLowerBound) and scanComplete is false. 409 scan_incomplete when where the set is used could not be checked everywhere. Deprecated: this is one of the five steps (set, version, publish, compile, activate) that POST /api/admin/identity-mapping/sets and PUT /api/admin/identity-mapping/sets/{id} run in one call, with the same checks and a release safety check made when the content is saved. It keeps working unchanged; new clients use the Mapping Set facade.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Field mapping set identifier.
Field mapping version identifier.
Header Parameters
Section titled “Header Parameters ”Idempotency key for state-changing operations that support replay protection.
Request Body required
Section titled “Request Body required ”object
object
Example
{ "snapshotId": "mapping_snapshot_123", "activationScope": { "clients": [ "web-app" ] }}Responses
Section titled “ Responses ”Field mapping activation response.
object
object
Example generated
{ "result": { "id": "example", "tenantId": "example", "fieldMappingSetId": "example", "fieldMappingVersionId": "example", "snapshotId": "example", "lifecycleState": "example", "activatedAt": 1, "holderId": "example", "alreadyActive": true }}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}The change was refused: the Mapping Set is named somewhere (referenced), the version would not meet what the references need (would_break_references), or where it is used could not be checked everywhere (scan_incomplete).
object
object
Everything found, other tenants’ included.
True when a place held more rows than were read.
The first references the caller may see in full.
object
The tenant the reference is in. Absent for the platform’s own default.
The entity ID of the SAML partner the provider is configured for.
A federation trust source whose runtime resolution names the set.
A Mapping Set version the reference pins.
The compiled snapshot a credential profile version was published with.
When asked about a Destination Profile, the Mapping Set the reference is through.
References in other tenants the caller may not see, as counts only.
object
False when the other tenants’ Core databases were not read (the caller has no global authority): the counts then hold only what the Admin database knows.
object
object
Given only for the caller’s own tenant, or to a caller with global authority.
A fixed code (for example core_database_unavailable, no_such_table).
Only on would_break_references, the condition the version would fail.
object
Example
{ "error": "conflict", "reason": "referenced", "references": { "items": [ { "kind": "platform_default", "federationRole": "saml_idp", "role": "issuance" } ], "unscanned": { "items": [ { "area": "platform_settings" } ] }, "violation": { "code": "destination_profile_invalid" } }}Error response.
object
Example generated
{ "error": "example", "message": "example", "error_description": "example"}