Closed jnweiger closed 11 months ago
Fix on the WND side -> https://github.com/owncloud/windows_network_drive/pull/472 . As said in the PR, it's targeting the release branch.
It makes more sense that WND matches whatever LDAP is exposing.
Confirmed fixed with https://github.com/owncloud/windows_network_drive/pull/472 -> windows_network_drive-2.4.0-rc.2 Also lower case works. The Attribute name must be written consistently either both upper case or both lower case, in user_ldap advanced settings and windows_network_drive config. OK.
Seen in user_ldap-0.19.0 with windows_network_drive 2.4.0 and core 10.13.0
The ldap schema has:
in Admin -> Settings -> User Authentication -> Advanced we want to allow the
homeDirectory
attribute as an Exposed Attributein config.php we want to (mis)use the
homeDirectory
attribute to map the uid lemming0123 to Alice:In Admin -> Storages, we mount a WND drive using the
ad01_lem
data ID(Optionally) patch the error message windows_network_drive/lib/kerberos/usermappings/ealdapattr.php to include more details:
When user lemming01234 wants to access their
lemming-wnd
folder, an error occurs:Expected behavior
Workaround
homedirectory
in all lower case in Admin -> Settings -> User Authentication -> Advanced -> Exposed Attribute