nextcloud-server.git - Nextcloud server, a safe home for all your data: https://github.com/nextcloud/server

	Commit message (Collapse)	Author	Age	Files	Lines
*	chore(IGetRealUIDBackend): Fix typo in doc block	Ferdinand Thiessen	2024-09-02	1	-1/+1
\| \| \| \|	Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
*	chore: Add SPDX header	Andy Scherzinger	2024-05-24	1	-20/+2
\| \| \| \|	Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
*	composer run cs:fix	Côme Chilliet	2023-01-20	1	-1/+0
\| \| \| \|	Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
*	Update php licenses	John Molakvoæ (skjnldsv)	2021-06-04	1	-2/+2
\| \| \| \|	Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
*	Improve search results when only phonebook-matches can we autocompleted	Joas Schilling	2021-03-17	1	-1/+1
\| \| \| \|	Signed-off-by: Joas Schilling <coding@schilljs.com>
*	Update license headers	Christoph Wurst	2019-12-05	1	-1/+3
\| \| \| \|	Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
*	Get the proper UID	Roeland Jago Douma	2019-08-13	1	-0/+44
	Some user backends (like the database backend) allow us to obtain a user case insensitive. However the UID itself is case sensitive. Example: * create a user User1 * login as User1 - This results the data/User1 folder to be created etc * now have some code somewhere that obtains the userFolder (from IRootFolder) but pas in 'uSER1' as uid - The code will check if that is a valid user. And in this case it is since User1 and uSER1 both map to the same user - However the the UID in the user object is used for the folder a new folder fill be create data/uSER1 With this PR this is avoided now. Since we obtain the real UID casing in the backend before creating the user object. Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>