Hello Quanah,
Thank you for your reply.
Do I create a new schema file for my new attribute as in ${new_attribute}.schema and another for the new object using this new attribute?
Sincerely,
Igor Shmukler
On Tue, Dec 2, 2014 at 11:05 PM, Quanah Gibson-Mount quanah@zimbra.com wrote:
--On Tuesday, December 02, 2014 10:55 PM +0200 Igor Shmukler igor.shmukler@gmail.com wrote:
Hello,
I want to have an ability add "custom attribute[s]" to my LDAP records. For example, such an attribute could be sipTelephone, mobile and/or something else.
I did a little digging. Please advise whether I am on the right track.
My understanding, at present, is that I would have to modify core.schema [located on my Ubuntu under /etc/ldap/schema ] and perhaps some other schema files from the same directory.
I found various syntax OIDs. For telephones, for example - 1.3.6.1.4.1.1466.115.121.1.50 should be the right one. There is another OID for strings - 1.3.6.1.4.1.1466.115.121.1.15 for UTF-8 coded strings.
Is editing core.schema the correct way to go? I am eagerly looking for advice.
Never, ever, edit core.schema.
You can apply for your own OID, create your own attributes, and then create objectClasses that use them. That is the correct way to do things.
--Quanah
--
Quanah Gibson-Mount Server Architect Zimbra, Inc.
Zimbra :: the leader in open source messaging and collaboration
Igor Shmukler wrote:
Do I create a new schema file for my new attribute as in ${new_attribute}.schema and another for the new object using this new attribute?
When using static configuration one usually uses include to add schema declarations to the configuration.
Personally I put attribute type and object class descriptions which more or less belong together into one .schema file. When including schema files the order is important.
Ciao, Michael.
On 2/12/2014 11:12 μμ, Igor Shmukler wrote:
Do I create a new schema file for my new attribute as in ${new_attribute}.schema and another for the new object using this new attribute?
See also: http://www.openldap.org/devel/admin/schema.html
We have done it in this way: Got a registered OID from IANA (as described in the above document), and then created custom schemas.
Nick
openldap-technical@openldap.org