]> Microsoft

mwahl@microsoft.com

Okta

danny.zollner@okta.com

Microsoft

pamela.dingle@microsoft.com

Nextident

ismael@nextident.ai

Security System for Cross-domain Identity Management Internet-Draft The System for Cross-domain Identity Management (SCIM) specifications are designed to make identity management in cloud-based applications and services easier. This document provides a platform-neutral schema for representing AI agents' identities in SCIM JSON format, enabling them to be transferred using the SCIM protocol between a client and service provider. This establishes an agentic identity so that an agent can subsequently be authenticated and authorized to interact with the service. About This Document Status information for this document may be found at . Discussion of this document takes place on the System for Cross-domain Identity Management Working Group mailing list (), which is archived at . Subscribe at .

Introduction The SCIM protocol and core schema are widely implemented for provisioning records for users into services. The default schema for those user records includes attributes such as a person's name, job title, and email address. This enables a SCIM client to inform a SCIM service provider of a new user, so that user can be identified in and subsequently authenticated to the service. SCIM also enables lifecycle controls for the SCIM client to update and remove that user record in that service, and associate that user with groups, roles and entitlements. With the growth of agentic AI, agents will also need to be able to interact with services. Some services will require an agent to have an identity represented within them in order to interact with resources. The attributes of an agent identity in a SCIM service can be different from the attributes of a human user identity. Similar to users, however, an agent's identity can have access rights in the service, represented through relationships of the agent's identity with groups, roles and entitlements in a service. As SCIM is familiar within the enterprise and agents often need the same lifecycle signals and group, role or entitlement memberships as users, defining a schema to transport agentic identities using the SCIM protocol simplifies deployment and enables subsequent authentication interactions and consistent controls for those agents' identities and access rights.

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Agent Resource Type This specification defines a new SCIM resource type and an accompanying core schema, following the resource type and schema conventions of :

Agent

A resource of this type represents an agent's identity to the service. It includes attributes of an agent's identity needed to be known by a service.

Resources of this type are conveyed via the SCIM protocol using JSON . Extension schemas can be defined to extend this resource type, allowing additional attributes. The core schema for the Agent resource type is identified by the URI "urn:ietf:params:scim:schemas:core:2.0:Agent". The schema defines the attributes described in the following sections. In addition, Agent resources include the common attributes "externalId", "id", "meta", and "schemas" as described in Sections 3 and 3.1 of .

Core Schema

Single-valued Attributes The Agent core schema defines the following single-valued attributes. A SCIM service provider that implements this specification MUST implement all attributes defined in the core Agent schema unless otherwise specified.

active

A boolean value indicating the agentic identity's administrative status. A SCIM client can indicate that an agentic identity is to be treated as inactive by the service by setting it to false. The definitive meaning of this attribute is determined by the SCIM service. REQUIRED.

description

The value of this attribute is a string with the agentic identity's human-readable description.

displayName

The value of this attribute is a string with the human-readable name of the agentic identity, suitable for display to end-users. REQUIRED.

agentUserName

A string containing a unique identifier for the agent, similar to a user's userName or email address. This value SHOULD be human-readable and MUST be unique across all Agent resources in the provisioning domain. REQUIRED.

Multi-valued Attributes The Agent core schema defines the following multi-valued attributes.

owners

A list of the responsible parties for an agentic identity. Each value is a complex type that allows referencing the "id" attribute of a user, a group, or other resource already known to the SCIM service provider. Each value has the following sub-attributes.

value

The "id" of the SCIM resource representing an owner of an agentic identity. This sub-attribute MUST be included for each "owners" value; mutability is "immutable".

$ref

The URI of the SCIM resource representing an owner of an agentic identity. RECOMMENDED; mutability is "readOnly".

displayName

The displayName of the agentic identity's owner. OPTIONAL; mutability is "readOnly".

Agent Resource Schema The following is a non-normative example of the Agent resource type as returned from the "/ResourceTypes" endpoint, in JSON format. The following is a non-normative example of the Agent schema as returned from the "/Schemas" endpoint, in SCIM JSON schema format. The following is a non-normative example of an Agent resource instance in JSON format.

Updates to Existing Schema To allow an agentic identity to be a member of a group, this memo augments the definition of the "members" attribute of as follows:

• allow the referenceTypes of the members "$ref" sub-attribute to also refer to an Agent resource
• allow the canonicalValues of the members "type" sub-attribute to also allow for "Agent"

Security Considerations SCIM data is intended to be exchanged using the SCIM protocol. It is important when handling data to implement the security considerations outlined in Section 7 of .

Privacy The text of this privacy section is derived from the corresponding privacy section of . Information should be shared on an as-needed basis. A SCIM client should limit information to what it believes a SCIM service requires, and a SCIM service should only accept information it needs. Clients and servers should take into consideration that sensitive information is being conveyed across technical (e.g., protocol and applications), administrative (e.g., organizational, corporate), and jurisdictional boundaries. In particular, information security and privacy must be considered. Security service level agreements for the handling of these attributes are beyond the scope of this document but are to be carefully considered by implementers and deploying organizations. Please see the Privacy Considerations section of for more protocol-specific considerations regarding the handling of SCIM information.

IANA Considerations

New Schema When published as an RFC, the IANA is requested to add the following addition to the "SCIM Schema URIs for Data Resources" established in :

URN	Name	Reference
urn:ietf:params:scim:schemas:core:2.0:Agent	Agent	This memo, Section 3

Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. The System for Cross-domain Identity Management (SCIM) specifications are designed to make identity management in cloud-based applications and services easier. The specification suite builds upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. Its intent is to reduce the cost and complexity of user management operations by providing a common user schema and extension model as well as binding documents to provide patterns for exchanging this schema using HTTP. This document provides a platform-neutral schema and extension model for representing users and groups and other resource types in JSON format. This schema is intended for exchange and use with cloud service providers. The System for Cross-domain Identity Management (SCIM) specification is an HTTP-based protocol that makes managing identities in multi-domain scenarios easier to support via a standardized service. Examples include, but are not limited to, enterprise-to-cloud service providers and inter-cloud scenarios. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. SCIM's intent is to reduce the cost and complexity of user management operations by providing a common user schema, an extension model, and a service protocol defined by this document. JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.

Changes From Earlier Versions This is the initial version of this draft.

Acknowledgments The editor would like to acknowledge the contribution and work of the authors of the SCIM RFCs and and of other SCIM Internet-Drafts, the participants of the IETF SCIM WG, and the SCIM Community.