This repository has been archived by the owner on Jan 27, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Need user id as UUID adjustments #41
Labels
bug
Something isn't working
Comments
Line 24 in 614ddec
|
ocis-accounts on-disk show that user1 was created by user id:
with user1 entry:
this is the einstein entry:
|
Merged
PR for the update #42 |
If alphanumeric account uuids are expected / allowed, we need to adapt the input validation in ocis-settings. It enforces the provided account uuid to be empty or a valid uuid. |
Validation for uuid is here: ocis-settings/pkg/service/v0/validator.go Line 62 in 614ddec
We'd need to change that (and adjust tests) to allow alphanumeric ids. |
We should not enforce the userid to be a uuid. it might be provided by other means, eg. legacy systems might migrate the username and use it as the uuid to prevent federated sharing ids from breaking. |
PR here for validation adjustment: #44 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
BLOCKS owncloud/ocis#409
Steps
replace github.com/gomodule/redigo => github.com/gomodule/redigo v1.8.2
yarn build-all
PHOENIX_ASSET_PATH=~/work/workspace/phoenix/dist PHOENIX_WEB_CONFIG=~/work/workspace/phoenix/config-ocis.json bin/ocis-phoenix --log-level debug server
and point at the correct settingsyarn run acceptance-tests tests/acceptance/features/webUICreateFilesFolders/createFolderEdgeCases.feature:58
Expected result
Call "value-list" has no error.
No notification.
Actual result
Notification "Failed to load settings"
400 Bad request for "value-list" call:
account_uuid: must be a valid UUID.
OCIS log:
so in the case of "user1" it's using "user1" as the UUID instead of a true uuid.
Maybe the Phoenix tests setup is not creating the test users properly ?
@individual-it @kulmann
The text was updated successfully, but these errors were encountered: