Open kulmann opened 2 months ago
Is there a valid reason to hardcode them?
I think the only remaining reason is the hardcoded default role-assignments in the settings service: https://github.com/owncloud/ocis/blob/master/services/settings/pkg/store/defaults/defaults.go#L353
Related ticket: https://github.com/owncloud/ocis/issues/9927 (and probably the better way to address this)
Describe the bug
When playing around with OCM I noticed (again) that uuids of the demo users are hardcoded, which makes them unusable for OCM tests. See details below:
Steps to reproduce
A
create an OCM invitationB
use the OCM invitation to accept the federated connectiontest
and open theSharing
panel in the sidebarExternal
as user type and search forEinstein
Einstein
is shown ✅Einstein
and create the shareExpected behavior
External
einstein
is shown as share receiverActual behavior
Internal
einstein
is shown as share receiver since botheinstein
s have the same uuid and then oCIS seems to prefer the internal user.Thoughts
This is not really a software bug, as we expect the uuids to be unique! But maybe it is possible to randomize the uuids of the demo users? Is there a valid reason to hardcode them? Or did we just never have the need to make them unique? For OCM demo purposes it would be important.