Question: should `meta` be marked as a required property for `/ResourceTypes` discovery endpoint?

[seikenberry9]

We are implementing a SCIM server using the elimity scim library. When testing compliance with this utility, the following error is returned for the /ResourcesTypes endpoint: error: object has missing required properties (["meta"]).

The SCIM RFC seems to read that meta is not required to be in the response from discovery endpoints:

Each SCIM resource (Users, Groups, etc.) includes the following common attributes. With the exception of the "ServiceProviderConfig" and "ResourceType" server discovery endpoints and their associated resources, these attributes MUST be defined for all resources, including any extended resource types.

Should meta be required in the response from the discovery endpoint? Thanks!

[suvera]

Yes, in a SCIM 2.0 server response for the /ResourceTypes endpoint, the meta attribute is mandatory.

The meta attribute provides essential metadata about the resource type itself, such as:

• resourceType: The name of the resource type (e.g., "User", "Group").
• created: The date and time when the resource type was created.
• lastModified: The date and time when the resource type was last modified.
• location: The URI of the resource type.

This information is crucial for clients interacting with your SCIM server, as it helps them understand the structure and capabilities of the supported resource types.

Key Points:

• Mandatory: The SCIM 2.0 specification explicitly states that the meta attribute is required for all resource types.
• Metadata: The meta attribute provides metadata about the resource type, not the individual resources themselves.
• Client Understanding: This information helps clients understand the capabilities of your SCIM server and how to interact with the different resource types it supports.

If you omit the meta attribute, your SCIM server will not be compliant with the SCIM 2.0 specification, and clients may encounter issues when trying to interact with it.