Rsk.AspNetCore.Scim 8.0.0

SCIM List Responses - Consistent Property Names

Historically, the SCIM list response has used inconsistent casing for the Resources property. To align with the SCIM specification, responses from endpoints that return a SCIM list, such as /Schemas and /ResourceTypes, will now consistently use an uppercase "R" for Resources. E.g.

{
    "totalResults": 1,
    "itemsPerPage": 1,
    "startIndex": 1,
    "schemas": [
        "urn:ietf:params:scim:api:messages:2.0:ListResponse"
    ],
    "Resources": [
        {
            "schemas": [
                "urn:ietf:params:scim:schemas:core:2.0:ResourceType"
            ],
            "endpoint": "/users",
            "schema": "urn:ietf:params:scim:schemas:core:2.0:User",
            "schemaExtensions": [
                {
                    "schema": "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User",
                    "required": false
                }
            ],
            "id": "User",
            "name": "User",
            "description": "User Account",
            "meta": {
                "resourceType": "ResourceType",
                "location": "https://localhost:5001/SCIM/ResourceTypes/User"
            }
        }
    ]
}

ResourceTypes Metadata Endpoint - Return Correct Meta Location

This release addresses an issue where the /ResourceTypes endpoint's response incorrectly listed the location of a ResourceType in the `meta` property. Now, a ResourceType in the Resources collection will have the correct meta location. E.g.

{
  ...
  "schemas": [
      "urn:ietf:params:scim:schemas:core:2.0:ResourceType"
  ],
  "meta": {
      "resourceType": "ResourceType",
      "location": "https://localhost:5001/SCIM/ResourceTypes/User"
  }
  ...
}

This release enhances the logging for a 500 error that occurs when processing a request to retrieve a resource by its ID. Previously, if the resource returned from the SCIM store's `FindById` method had a null or empty ID field, the SCIM component would respond with a 500 error and an unclear message. Now, the SCIM component will provide a clear message explaining the reason for the request failure.