"LDAP user and group backend" and access via WebDAV

ℹ️ Support
1

Hi everybody,

after running into WebDAV issues with Windows 10 (I described it in detail here) I’m facing another problem with WebDAV now.

Nextcloud version (eg, 10.0.2): 11.0.1
Operating system and version (eg, Ubuntu 16.04): Debian GNU/Linux 8 (jessie)
Apache or nginx version (eg, Apache 2.4.25): Apache 2.4.10-10+deb8u7
PHP version (eg, 5.6): 5.6.30+dfsg-0+deb8u1
Is this the first time you’ve seen this error and can you replicate it?: Error occurs across different installed instances.

I’m using the “LDAP user and group backend” to authenticate my users with login names like FIRST.LAST@DOMAIN.TLD. Everything works fine now but when accessing their files via WebDAV I cannot use a path like

https://cloud.DOMAIN.TLD/remote.php/dav/files/FIRST.LAST@DOMAIN.TLD/

but instead I have to use a path like

https://cloud.DOMAIN.TLD/remote.php/dav/files/UUID/

That means via WebDAV access the login name isn’t recognised in the path (I’m only seeing an empty folder) but you have to use the UUID which is internally assigned to the user (what makes it hard for a normal user to configure access for himself). For the login credentials (username and password) the FIRST.LAST@DOMAIN.TLD works fine.

Probably the WebDAV backend isn’t provided with the mapping of login name and internal UUID and therefore does not allow access?

Where should I suggest this as feature request?

Thanks in advance!

2

Well, this one is a little embarrassing for me: I should have read the docs correctly…

You just have to set the “Internal Username” on the tab “Expert” of the LDAP configuration according to your wish, e.g. to “mail”. Then the folders on disk get created not as UUID but as FIRST.LAST@DOMAIN.TLD and are accessible as such via WebDAV, too (as it is even mentioned in the help text).

And, of course, you should do this before any user logs in the first time as then the folders get created.