On 04/23/2013 10:40 PM, Drew Gibson wrote:
Hi,
After deleting OC 4.5 and installing OC 5, the user data directories are
now named with hex UIDs rather than the user login name that was there
before.
Is this expected behaviour?
This string is also returned by OC_User::getUser() resulting in some
strange greetings in notification emails and other places.
e.g.
data/83C6A05A-EF02-4911-AAAA-48EF868C1167
data/9CB311DB-D74B-4926-BC7E-94B3B3FE9323
data/admin
data/AF4680DB-CF4A-400A-983F-FCF28BD47964
data/D066D453-D96D-4D96-B0A5-6EFAA2611F92
You can set the "User home folder naming rule" (Advanced LDAP settings,
Special attributes) to avoid that. In the notifications the "User
Display name field" is used (Advanced LDAP settings, Directory section).
If you want to make sure OC doesn't use these UUIDs at all, you can also
overwrite the value of the "owncloud_name" in the "oc_ldap_user_mapping"
table of the OC database, right after creating the user, but before
anyone has a chance to log in.
Yours: Laszlo
I am using the "LDAP user and group backend" app for authentication
against a Microsoft Active Directory database.
LDAP settings:
User Login Filter
sAMAccountName=%uid
User List Filter
objectClass=person
User Display Name Field
cn
regards,
Drew
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
