ModelOAuth module
CimdClient
OAuth client identified via Client ID Metadata Document
(draft-ietf-oauth-client-id-metadata-document).
Auto-registered on first sighting of an HTTPS-URL client_id by CimdClientResolver.
The CIMD URL itself lives inside clientMetadata (the validated CIMD document JSON).
The framework distinguishes these rows via:
- the entity discriminator column (= 'OAuth\Entities\CimdClient')
- oauthClientId is a synthetic 'cimd_<sha256_first_27hex>' value
Subsequent refreshes from the upstream metadata document will overwrite any manual
edits — the document is the source of truth. Any future admin-edit UI should warn
the operator that edits are transient. Delete cascades through FK relationships to
revoke all derived grants — that is the canonical revocation path for a CIMD client.
A model in the OAuth module, with 3 members for templates, 3 API properties and 3 members for admin templates.
Templates view
Properties 3
Take no arguments.
No members match the filter.
API & Jobs view
API & JobsEach property is a key in REST API responses and job payloads. Its name is the template getter without get, is or has. Methods that need arguments are not available here.
Properties 3
Read-only values on the record.
No members match the filter.
Admin view
AdminAvailable in cdna-admin templates. Copy an admin template into your site repository to change how this record is edited.
Properties 3
Take no arguments.
No members match the filter.