Open tetebueno opened 1 week ago
Can I work on it
Anyone is free to work on issues... however I think it's possible a whitespace user name could exist if it was created before validation prevented it (that was added in 10.8.0).
so what to do if whitespace user already exists
Such user wouldn't be able to login to the web app. Is it possible that he'd be able to login to other Jellyfin apps?
So I have to stop whitespace name users by trimming the string
We can't do this unless there is a server migration to fix those user names.
All right so who is going to do migrations
Whoever has the motivation and ability... that's the nature of our project structure 🤷‍♂️
How would a migration be carried out? IE. What would we do with those whitespace usernames? If we automatically replace the whitespace with another specific character, that could lead to brute force attacks against usernames of that character. Maybe replace it with "User" + random number?
I'm not sure what would be the best approach... that is a conversation to have with the server team.
From a frontend standpoint this is blocked until we have migrated the usernames that would be impacted.
I thought as much. I created a discussion on this here https://github.com/jellyfin/jellyfin/discussions/12967
Describe The Bug As stated in the title, username can't be empty, but it can be blank.
Steps To Reproduce
Expected Behavior Login form should trim the value and show the same warning as when leaving the field empty.
Logs
Screenshots
System (please complete the following information):
Additional Context N/A