[ ispman-Bugs-1429276 ] Duplicate OID in ispman LDAP schema.
"SourceForge.net" <[email protected]> Fri, 10 Feb 2006 10:12:55 -0800
| Newsgroups | gmane.comp.isp.ispman.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #1429276, was opened at 2006-02-10 19:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1429276&group_id=8390 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Yacine K (yacine) Assigned to: Nobody/Anonymous (nobody) Summary: Duplicate OID in ispman LDAP schema. Initial Comment: Hi, I would like to use ispman 1.3 with FDS (aka fedora- ds): http://directory.fedora.redhat.com/wiki/Main_Page and I found âÂÂI guessâ a bug in ispman.schema. To import ispman schemas (or any other openldap schemas) on FDS, a conversion must be done because FDS is strict RFC compliant: http://directory.fedora.redhat.com/wiki/Howto:OpenLDAP Migration We have done our own script because scripts in URL above do not process ispman schemas in an efficient way. So it works perfectly for any openldap schemas but not for the ispman openldap schema. I discover that ispman.schema is using a few time the same OID for object class and attribute declaration !!! Below the type of error reported by FDS: [08/Feb/2006:20:44:21 -0500] dse - The entry cn=schema in file /opt/fedora-ds/slapd- ldapmst01/config/schema/84ispman.ldif is invalid, error code 20 (Type or value exists) - object class ispmanProcesses: The OID "1.3.6.1.4.1.8833.2.1.1007" is also used by the attribute type "ispmanCurrUid" After investigation this type of declaration does not seem to be RFC compliant: this is why I doing a bug report. I do not know why openldap accept this type of duplicate OID but IMHO OID must be unique by definition. I did not test the latest openldap version but I guess sometime openldap will also take care of this type of âÂÂbogusâ schema declarations. It could be interesting to have some feedback from people which are using NDS, Sun or any other LDAP server to see if they have had the same issue. If you correct it then it will be ok for new installations but may create some upgrade/migration issues, to be validated. Regards, Yacine (aka Yada on IRC). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108390&aid=1429276&group_id=8390 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642