[Date Prev][Date Next]
RE: old objectclass format not supported
Looks like you're using InterlinkNetworks AAA radius server. In their
current release they include an LDAPv3 version of their schema so there is
no need to bother with the old format file. It's really not feasible to
simply convert from the old format to the current format because more
information is required in the new format.
-- Howard Chu
Chief Architect, Symas Corp. Director, Highland Sun
Symas: Premier OpenSource Development and Support
> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Jeff Neuffer
> Sent: Thursday, December 20, 2001 1:46 PM
> To: openldap-software@OpenLDAP.org
> Subject: old objectclass format not supported
> I'm running OpenLDAP 2.0.11.
> I'm trying to include an addidtional schema file (with radius
> attributes) and when I do I get an error message that says,
> "Dec 20 15:41:30 radius00 slapd:
> /etc/openldap/schema/slapd.user_oc.schema: line 797: old objectclass
> format not supported."
> I checked /etc/openldap/core.schema and compared it to the one I am
> including in my slapd.conf file.
> Here is a sample of the differences,
> --- From core.schema,
> attributetype ( 184.108.40.206 NAME 'createTimestamp'
> EQUALITY generalizedTimeMatch
> ORDERING generalizedTimeOrderingMatch
> SYNTAX 220.127.116.11.4.1.1418.104.22.168.24
> SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation )
> --- From slapd.user_at.schema,
> attribute aaaCheck 2.16.840.1.11422.214.171.124 cis
> I assume these are different LDAP versions? If so, is there a tool that
> can convert from one format to another? If not, will OpenLDAP (2.0.x)
> accept older LDAP protocol versions?