You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the version attribute returned by the SCIM server in the meta section of a resource is a number. The RFC for SCIM 2 indicates this should be an ETag. Most implementations I've worked with (and indeed all of the RFC examples) have this attribute as a string, so our parsing logic falls down when this SCIM server returns a number.
The issue has been fixed in the Release503 branch.
The version property of a representation is now returned as a string.
By default, the version is an integer that increments each time a modification is made to the representation. However, you can define your own versioning logic by implementing the following interface:
public interface IRepresentationVersionBuilder
{
string Build(SCIMRepresentation representation);
}
public class CustomRepresentationVersionBuilder : IRepresentationVersionBuilder
{
public string Build(SCIMRepresentation representation)
{
return Guid.NewGuid().ToString()
}
}
Currently, the version attribute returned by the SCIM server in the meta section of a resource is a number. The RFC for SCIM 2 indicates this should be an ETag. Most implementations I've worked with (and indeed all of the RFC examples) have this attribute as a string, so our parsing logic falls down when this SCIM server returns a number.
See: https://datatracker.ietf.org/doc/html/rfc7643#section-3.1
The text was updated successfully, but these errors were encountered: