-
Notifications
You must be signed in to change notification settings - Fork 184
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
GraphAPI groups are case in-sensitive #4291
Comments
Just like usernames the groupnames are case-insensitive in ocis. That means @micbar is there a requirement to have case-sensitive groups names in ocis somewhere? |
@rhafer @kiranparajuli589 IMO we need to follow the LDAP standard here. Can you adjust the tests that they don't expect a case sensitive group name? |
@kiranparajuli589 probably we can just skipOnOcis any of the core API tests that check that group names are case-sensitive. And then add a couple of scenarios to the oCIS local API tests that demonstrate that group names like |
Note: for any "parallel deployment" implementation, this is going to be one "feature" that will be different between the oC10 core side and the oCIS side. If anyone really has existing different groups called |
core tests adjusted with owncloud/core#40301 & new tests added with #4422 |
(leftover from #3167)
While using the GraphAPI to create groups, we cannot create groups with case-insensitive names like:
In Graph API group names are case in-sensitive. Meaning, we these 3 groups cannot be added at the same time.
We can only create one group and then,
500
is returned with theEntry Already Exists
message.Also, groups can be fetched with the
displayName
value but it is case-insensitive. If I have a group with the namefootball-lovers
. Then, the following request works perfectly fine.This feature is not the same as the
oc10
server.Acceptance tests are demonstrated here.
See also this comment for more ref.
The text was updated successfully, but these errors were encountered: