Closed joachimLengacher closed 11 months ago
Here's a proposal for a fix along with a test that also highlights the requested change: https://github.com/pingidentity/scim2/pull/190
Thanks for reporting this, @joachimLengacher. I'll look more into this, but at first glance, it seems appropriate to update these values on the Group
class. The RFC seems clear about this.
@kqarryzada I just discovered a potential other problem: in GroupResource
the multiValueClass
is com.unboundid.scim2.common.types.Group
where the return type is List<Member>
. I guess that the multiValueClass
should be com.unboundid.scim2.common.types.Member
because com.unboundid.scim2.common.types.Group
is also used in the UserResource
:
@Attribute(description = "A list of members of the Group.",
isRequired = false,
mutability = AttributeDefinition.Mutability.READ_WRITE,
returned = AttributeDefinition.Returned.DEFAULT,
multiValueClass = Group.class)
private List<Member> members;
I will update that in my PR too...
The code change for this issue has been committed to master. Thanks for reporting this.
Describe the bug According to the RFC, the sub-attributes of the
group
resource'smember
attribute should beimmutable
instead ofreadOnly
.To Reproduce Call the
/Schemas
endpoint. Themutability
isreadOnly
for all sub-attribute of themember
attribute instead ofimmutable
, see the$ref
attribute, for example:Expected behavior The values of
mutability
of all the sub-attributes should beimmutable
.Additional context