# AZ720: SCIM settings that don't hold

`authz.set_scim` names what the SCIM endpoint (`authz.scim`) reads, as one JSON object that replaces the stored settings: `principal` (whose API key signs the identity provider in, as `type:id`), `group` (a relation `authz.sync_members` takes, as `type.relation`) with `group_name`, `group_external_id` and `group_function`, `user_name`, `user_external_id`, `user_active`, `user_resource` and `user_function`, and `page`. Each is checked when it is set, and the message says which one doesn't hold and why: a name that is no setting, a principal no row is or whose type doesn't sign in, a relation with no single table of members, a column the table doesn't have (or one of another type: `user_active` names a boolean, `user_resource` a jsonb), a function that isn't `(text, jsonb) RETURNS text`, written with its schema and owned by the policy's owner (it is called with the owner's rights, so a function another role may rewrite is refused), a page that is no number from 1 to 1000. Nothing is stored then: the settings stay as they were. The call is the owner's (an administrator's, a deploy step's), not a request's: the SDKs give this error no answer of its own, and a request that met it would be left an error, a 500. SQLSTATE 22023.

Reported to the app, by the `authz.*` functions and the policy's rules: the code is in the error's HINT (`rowstile help AZ720`), and the SDKs' errors carry it as `code`.
