New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cases 4.4/5.4/5.5/5.6, Handling of immutable attribute #44

Closed
jgomer2001 opened this Issue Oct 23, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@jgomer2001
Collaborator

jgomer2001 commented Oct 23, 2017

From SCIM Test Cases.xlsx

4.4 Create a user with an immutable attribute
5.4 Update an immutable attribute that was previously null - value should be set
5.5 Update an immutable attribute that has a value, setting it to the same value - should succeed
5.6 Update an immutable attribute that has a value, setting it to a different value - should fail

@jgomer2001 jgomer2001 added this to the CE 3.2 milestone Oct 23, 2017

@jgomer2001 jgomer2001 self-assigned this Oct 23, 2017

@jgomer2001

This comment has been minimized.

Collaborator

jgomer2001 commented Oct 23, 2017

Core schema does not define any immutable attribute for user resource. Custom attributes part of user extension are assumed to follow the default values for all the attributes characteristics:

  • required,
  • canonicalValues,
  • caseExact,
  • mutability,
  • returned,
  • uniqueness

However, immutable attributes manipulation is now supported for any resource that by definition contains such kind of attributes in its core schema. For example the sub-attributes of member in Group resource and some attributes in the Fido Device resource.

Test cases being written to validate proper behavior.

jgomer2001 added a commit that referenced this issue Jan 3, 2018

jgomer2001 added a commit that referenced this issue Jan 3, 2018

@jgomer2001

This comment has been minimized.

Collaborator

jgomer2001 commented Jan 3, 2018

Other relevant test cases: PatchGroupTest#patch3, FidoDeviceTest

@jgomer2001 jgomer2001 closed this Jan 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment