Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Handle user names in case-insensitive manner in the Ampache and Subsonic APIs #1147

Closed
paulijar opened this issue May 28, 2024 · 1 comment
Closed

Handle user names in case-insensitive manner in the Ampache and Subsonic APIs #1147

paulijar opened this issue May 28, 2024 · 1 comment
Labels
6 - Ready for release Fix or feature is ready and will be included in the next release Enhancement

Comments

@paulijar
Copy link
Collaborator

Both ownCloud and Nextcloud interpret the user names in case-insensitive manner during the log in. That is, even though the user names are stored using the casing just as given during the creation, the user may log in by giving the same name with different casing. You can create a user called "SomeUser" and still log in by typing the user name as "someuser" or "SOMEUSER" or any other variant.

Meanwhile, the Ampache and Subsonic APIs of the Music app require the user name to be given using exactly the correct casing. This should be aligned with the standard login behavior of the clouds.

This was first brought up in icefields/Power-Ampache-2#117.
paulijar added a commit that referenced this issue May 31, 2024
@paulijar
Ampache/Subsonic: Case-insensitive user name checking
6a60e0d 
In the normal log-in of ownCloud and Nextcloud, the user names are allowed
using any casing. The same is true at least for Ampache proper. Now also the
APIs of the Music app follow the suite.

refs #1147
@paulijar paulijar added the 6 - Ready for release Fix or feature is ready and will be included in the next release label Jun 4, 2024
@paulijar
Copy link
Collaborator Author

This improvement has now been released in Music v2.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
6 - Ready for release Fix or feature is ready and will be included in the next release Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@paulijar