On 03/07/2013 01:25 PM, Tornóci László wrote:
On 03/07/2013 11:49 AM, Dirk Kastens wrote:
Hi,
seems that this was the wrong place.
Why? Did you truncate the oc_ldap_user_mapping table?
Could have been that something was left in the Cache, too.
Owncloud still used the UUID for
the user direct
On 03/07/2013 01:25 PM, Tornóci László wrote:
On 03/07/2013 11:49 AM, Dirk Kastens wrote:
Hi,
seems that this was the wrong place. Owncloud still used the UUID for
the user directory. Meanwhile I have changed line 431 in
user_ldap/lib/connection.php from
if(!in_array($this->config['ldapUuidAtt
Hi,
If I understand your problem correctly, you don't need to change the
source at so many places. There are many things here that can be easily
mixed up:
1. uid to login
2. internal ID for OC
3. user home dir path
4. display name
Your problem was that from OC5 the LDAP entryUUID was used for #
On 03/07/2013 11:49 AM, Dirk Kastens wrote:
Hi,
seems that this was the wrong place. Owncloud still used the UUID for
the user directory. Meanwhile I have changed line 431 in
user_ldap/lib/connection.php from
if(!in_array($this->config['ldapUuidAttribute'], array('auto',
'entryuuid', 'nsuniquei
Hi,
seems that this was the wrong place. Owncloud still used the UUID for
the user directory. Meanwhile I have changed line 431 in
user_ldap/lib/connection.php from
if(!in_array($this->config['ldapUuidAttribute'], array('auto',
'entryuuid', 'nsuniqueid', 'objectguid'))
to
if(!in_array($th
Hi Arthur,
You can patch it yourself by replacing
the line
https://github.com/owncloud/core/blob/master/apps/user_ldap/lib/access.php#L317
with
$intname = $isUser ? $this->sanitizeUsername($this->readAttribute($dn,
'uid')) : $this->sanitizeUsername($ldapname);
Great! I didn't know that this i
On 02/27/2013 08:56 AM, Dirk Kastens wrote:
Hi Arthur,
The problem is, that all other attributes may change (and may be not
unique) in the directory server.
At least, in our user management the uid is unique and never changes. It
is the same across all databases, be it LDAP, AD, or SQL. So I
Hi Arthur,
The problem is, that all other attributes may change (and may be not
unique) in the directory server.
At least, in our user management the uid is unique and never changes. It
is the same across all databases, be it LDAP, AD, or SQL. So I did
prefer the old owncloud configuration.
On 02/22/2013 11:09 AM, Dirk Kastens wrote:
Hi,
the LDAP backend is now using the entyUUID attribute to store users.
(tech detail: the uuid attribute will be autodetected, e.g. AD uses a
different one)
This could be a problem if you change your ldap server, maybe from
openldap to AD or to No
Hi,
the LDAP backend is now using the entyUUID attribute to store users.
(tech detail: the uuid attribute will be autodetected, e.g. AD uses a
different one)
This could be a problem if you change your ldap server, maybe from
openldap to AD or to Novell. Although the user data are the same (ui
On Tuesday, February 19, 2013 20:35 CET, Arthur Schiwon
wrote:
>
> Depends on where you tackle it. If you ensure uniqueness on LDAP side,
> you are not getting a problem on ownCloud as long as you don't use other
> user backends (which may have other problems). In some cases it is
> necessar
On 02/19/2013 02:55 PM, Andreas Ergenzinger wrote:
On Tuesday, February 19, 2013 12:36 CET, Arthur Schiwon
wrote:
I configure CN as the display name attribute. But display
names are not unique. So it's not possible to find the right user.
It's true that display names are not unique. But
On 02/19/2013 04:38 PM, Andreas Ergenzinger wrote:
On Tuesday, February 19, 2013 15:09 CET, Frank Karlitschek
wrote:
An admin can disable the option for users to change the display
name. I depends on the user scenario if this is useful and save or
Very good. I agree that editable display nam
On Tuesday, February 19, 2013 15:09 CET, Frank Karlitschek
wrote:
> An admin can disable the option for users to change the display name. I
> depends on the user scenario if this is useful and save or not. In case you
> use a directory like LDAP then we rely on a properly configured useracco
On 19.02.2013, at 08:55, Andreas Ergenzinger
wrote:
>
> On Tuesday, February 19, 2013 12:36 CET, Arthur Schiwon
> wrote:
>>> I configure CN as the display name attribute. But display
>>> names are not unique. So it's not possible to find the right user.
>
>>
>> It's true that display name
On Tuesday, February 19, 2013 12:36 CET, Arthur Schiwon
wrote:
> > I configure CN as the display name attribute. But display
> > names are not unique. So it's not possible to find the right user.
>
> It's true that display names are not unique. But would it help to number
> them? You would
On 02/19/2013 09:19 AM, Dirk Kastens wrote:
Hi,
the LDAP backend is now using the entyUUID attribute to store users.
(tech detail: the uuid attribute will be autodetected, e.g. AD uses a
different one)
I
don't know if this is such a good idea. Now, if you share a file, the
entryUUID is dis
Hi,
the LDAP backend is now using the entyUUID attribute to store users. I
don't know if this is such a good idea. Now, if you share a file, the
entryUUID is displayed instead of the uid (see attached picture). And in
the user list of the admin interface you see the entryUUIDs as the
loginnam
18 matches
Mail list logo
