You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 18, 2018. It is now read-only.
Hi, my LDAP backend and my CAS work perfectly ok.
However in my LDAP configuration I have set the Advanced > Special attributes > User Home Folder Naming Rule, to the value "homeDirectory".
This value comes from LDAP and tells owncloud that the files directory for each user, will be the one that is displayed on LDAP.
So if the user has LDAP directory /users/m/v/user, the local owncloud directory will also be /users/m/v/user
BUT, when I activate the CAS and do a login from the CAS, the local directory of the user is created into the DATA and not into the /users/m/v/user as expected.
Can you please tell me how to correct this problem?
The text was updated successfully, but these errors were encountered:
Hi, my LDAP backend and my CAS work perfectly ok.
However in my LDAP configuration I have set the Advanced > Special attributes > User Home Folder Naming Rule, to the value "homeDirectory".
This value comes from LDAP and tells owncloud that the files directory for each user, will be the one that is displayed on LDAP.
So if the user has LDAP directory /users/m/v/user, the local owncloud directory will also be /users/m/v/user
BUT, when I activate the CAS and do a login from the CAS, the local directory of the user is created into the DATA and not into the /users/m/v/user as expected.
Can you please tell me how to correct this problem?
The text was updated successfully, but these errors were encountered: