1 Topic by alex42

  • alex42
  • Member
  • Offline
  • Registered: 2013-08-26
  • Posts: 147

Topic: Changing LDAP schema - No problem?

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1
- Linux/BSD distribution name and version: Ubuntu 14.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
====

Hi,

iRedMail configures the LDAP to use the cn attribute as attribute for name and surname. Due to the fact that ownCloud has a problem with blanks in this field I would like to change the LDAP configuration. Here comes the OC bugreport:

https://github.com/owncloud/core/issues/26519

Will it produce problems if I use cn for the user's name and the sn for its surname?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,165

Re: Changing LDAP schema - No problem?

*) IMO, seems this is a OC bug, then push OC team to fix it. And according to the OC issue, it's VERY VERY VERY normal to store full name in "cn" attribute, and it's very normal to search LDAP with "*string*", not just "string*".

*) Anyway, if you still want to use different attribute to store name/surname, it's fine in this case. on iRedMail side, iRedAdmin stores full name in "cn", if you change it, you expect other strings (the one you set) appears as full name in iRedAdmin, and probably other LDAP client or LDAP integrated softwares.

BTW, this is not changing ldap "scheme".