Home / Draft tracker

draft-wzdk-scim-agent-resource-00

Status: Active individual draft · Checked 18 October 2026

The joint draft. It defines one resource type, Agent, with five attributes, and it is the base that other agent extensions build on.

What it defines

A new SCIM resource type called Agent, identified by the schema URN urn:ietf:params:scim:schemas:core:2.0:Agent. The draft says a resource of this type represents an agent's identity to the service. Servers that implement it must implement all attributes of the core schema, unless the draft says otherwise.

The core schema has five attributes:

• active (required)
• displayName (required)
• agentUserName (required, unique across the provisioning domain)
• description (optional)
• owners (optional, multi-valued)

It also changes one existing definition. The members attribute of groups in RFC 7643 may now point to an Agent, and the type of a member may be Agent. That lets you put agents into the same groups you use for roles and access.

Why the authors say it is needed

The introduction gives three reasons. Agents will need to interact with services. Some services will want an identity for the agent inside the service. And SCIM is familiar in enterprises, so agents can reuse the same lifecycle signals and group, role and entitlement memberships that users get.

What is deliberately small

This revision has no credentials, no application resource, no lifecycle states beyond the on/off flag, and no fields for roles or entitlements on the agent itself. The text says extension schemas can be defined to add attributes. The Oracle governance draft is exactly that kind of extension.

Where it came from

The joint draft sits after two earlier proposals, one from Microsoft and one from Okta. Its appendix says only "This is the initial version of this draft", and its acknowledgments thank the authors of the SCIM RFCs and of other SCIM Internet-Drafts. See the comparison on the draft tracker.

Status and what to expect

It is an individual Internet-Draft with Informational intended status. It is not a standard. Drafts are valid for a maximum of six months and may be replaced or obsoleted at any time, and the IETF text itself says it is inappropriate to cite them as anything other than "work in progress". This one expires on 7 December 2026. A new revision before that date is the normal way to keep a draft alive.

Facts on this page come from the text of the draft and its datatracker page, read on 18 October 2026. Drafts change, so check the datatracker for the current state. This site is independent and not affiliated with the IETF.

Compare with