-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Username 'meta' login problem #32547
Comments
When logging in as another ordinary username like
The code is finding the But when the username is |
See initial user report in comment #29207 (comment) |
"meta" is now used in the node API to access versions and other things. we need to:
@DeepDiver1975 FYI |
Hello! I've spent 8 hours resolving this "meta" problem after 9.1.8 -> 10.0.10.4 upgrade "meta" is my main user, admin and shares a ton of seperate folders to other 30 users. What are my options. Why don't you make an upgrade script that auto renames "meta" username to something else. Is it also possible that you don't make "meta" a reserved username? Thanks, Bojan |
Note: I'm sure there is another issue about other user names that do not work and should be prevented. But I am having trouble finding it right now. User
It does not crash right away, but something bad is going to happen with the
These ones are a problem because the storage of user's files sits in the same |
I think it is very dangerous to use such a common usernames for "system operations", expecially bloking them in version 10. If it would be version <=1.0 , the problem wouldn't great. I suggest renaming for example "meta" to "oc_api_metadata" and block creating new usernames staring with "oc_.." . I am quite sure no username collisions would occure in the future. BR, Bojan |
in general my suggestion would be to change the internal VFS and also the structure of the home folder to properly separate user data. Currently it's a legacy mess #18029. and then have all the meta, avatars, etc stuff also in an own folder. this way there wouldn't be any conflicts. so the homes would become "/users/vincent/files/..." instead of "/vincent/files". |
Everything should be an app. What about |
Hello! So, what is the best solution to solve this "meta" username problem?
Questions:
|
Following my comment on #18029 I have change my ldap configuration to use the UUID instead of the username as the home folder, but the issue actually remain. It seems to not only a path issue then but maybe also require that the user_id to not clash with those special folder? If I go in the DB I see that my user has a UUID for his home:
But when connecting I have the same issue has before:
|
PR #37268 has been merged. It prevents creating any of these "special" user names. That should be released in 10.5.0 If you find other "special" user names that should be banned, then please open an issue and they can easily be added to the list. |
Steps to reproduce
meta
meta
Expected behaviour
Normal login, skeleton files displayed.
Actual behaviour
"Internal server error"
Note: I added some
error_log()
calls to the variousnewFolder()
methods to see which one is being called and the value of$path
Server configuration
Operating system:
Ubuntu 18.04
Web server:
PHP dev server
Database:
mySQL
PHP version:
7.1.20
ownCloud version: (see ownCloud admin page)
Current core master from git
The text was updated successfully, but these errors were encountered: