You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by dBug31 <ni...@free.fr> on 2012/04/27 15:38:14 UTC
Re: Custom Schemas and Partitions
Hi, i have the same problem...
Any help please ?
Re: Custom Schemas and Partitions
Posted by karthik <kj...@teksystems.com>.
Pierre-Arnaud Marcelot <pa...@...> writes:
>
> Thanks for your reply.
>
> Happy to know it worked, finally.
>
> We'll be tracking this bug for the next release.
>
> Regards,
> Pierre-Arnaud
>
> On 27 avr. 2012, at 16:52, dBug31 wrote:
>
> > Yes i use the "ApacheDS Servers plugin embedded", it's more easy to use for a
> > beginner in LDAP like me...
> >
> > Thank you !
> >
> > It's working well with a name without uppercase.
> >
> > Thanks for you reactivity.
> >
> >
>
>
Thanks you guys. I seemed to have the same issue in creating a custom schema. I
had upper case in my name too and was driving me nuts to figure out what was
going on. Thanks to this post, I was able to get it fixed.
Just like the user of this post, I am using just the Apache Directory Studio
(Version 1.5.3) and the plugin. I am encountering a problem in the next step as
well. Although my new schema is created, I am unable to use the custom Object
class and the attributes in this schema to create a new object. Should I be
doing something else in order to be able to use those attributes/object classes?
Should I open a new thread on this or is this something that one of you can
help me out here.
FYI, I have also created a request on Apache.org requesting help on the same.
Jira Reference ID: DIRSTUDIO-831
reagrds,
Karthik
Re: Custom Schemas and Partitions
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Thanks for your reply.
Happy to know it worked, finally.
We'll be tracking this bug for the next release.
Regards,
Pierre-Arnaud
On 27 avr. 2012, at 16:52, dBug31 wrote:
> Yes i use the "ApacheDS Servers plugin embedded", it's more easy to use for a
> beginner in LDAP like me...
>
> Thank you !
>
> It's working well with a name without uppercase.
>
> Thanks for you reactivity.
>
>
Re: Custom Schemas and Partitions
Posted by dBug31 <ni...@free.fr>.
Yes i use the "ApacheDS Servers plugin embedded", it's more easy to use for a
beginner in LDAP like me...
Thank you !
It's working well with a name without uppercase.
Thanks for you reactivity.
Re: Custom Schemas and Partitions
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Actually I meant the server (ApacheDS).
Are you using the ApacheDS Servers plugin embedded in Apache Directory Studio (!= ApacheDS)?
In any case, I did further testing and I suspect we have a bug with schema names containing uppercased letters (I can't delete the imported schema, here on the trunk version of ApacheDS).
Looks like we're doing some fancy things with the lower-cased version of the schema name while we shouldn't.
Since all our bundled schemas are lowercased, we didn't notice this issue until now.
My advice would be to use a name for your schema that doesn't include any uppercased letter.
I'm confident it will work.
Thanks,
Pierre-Arnaud
On 27 avr. 2012, at 16:17, dBug31 wrote:
> I use : Version: 1.5.3.v20100330 is it correct ?
>
Re: Custom Schemas and Partitions
Posted by dBug31 <ni...@free.fr>.
I use : Version: 1.5.3.v20100330 is it correct ?
Re: Custom Schemas and Partitions
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Thanks.
What version of ApacheDS are you using?
It worked on the current trunk version.
Regards,
Pierre-Arnaud
On 27 avr. 2012, at 15:59, dBug31 wrote:
> dn: cn=schemaTAS, ou=schema
> objectclass: metaSchema
> objectclass: top
> cn: schemaTAS
> m-dependencies: system
> m-dependencies: cosine
> m-dependencies: inetorgperson
> m-dependencies: core
>
> #!RESULT OK
> #!CONNECTION ldap://localhost:10389
> #!DATE 2012-04-27T15:19:31.021
> dn: ou=attributeTypes, cn=schemaTAS, ou=schema
> objectclass: organizationalUnit
> objectclass: top
> ou: attributetypes
>
> #!RESULT ERROR
> #!CONNECTION ldap://localhost:10389
> #!DATE 2012-04-27T15:19:31.031
> #!ERROR [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for Add Request
> : ClientEntry dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1801, ou=attributeTypes,
> cn=schemaTAS, ou=schema objectclass: metaAttributeType objectclass:
> metaTop objectclass: top m-singleValue: TRUE m-oid:
> 1.3.6.1.4.1.1.0.4.3.2.1801 m-description: Adresse IP du serveur de l
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.15 m-name: IpAddress : ERR_10026 Cannot
> add the AttributeType m-oid=1.3.6.1.4.1.1.0.4.3.2.1801, ou=attributeTypes,
> cn=schemaTAS, ou=schema, as the associated schema (schematas) is not loaded]
> dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1801, ou=attributeTypes, cn=schemaTAS, ou=sc
> hema
> objectclass: metaAttributeType
> objectclass: metaTop
> objectclass: top
> m-oid: 1.3.6.1.4.1.1.0.4.3.2.1801
> m-name: IpAddress
> m-description: Adresse IP du serveur de l
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
> m-singleValue: TRUE
>
> #!RESULT ERROR
> #!CONNECTION ldap://localhost:10389
> #!DATE 2012-04-27T15:19:31.041
> #!ERROR [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for Add Request
> : ClientEntry dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1802, ou=attributeTypes,
> cn=schemaTAS, ou=schema objectclass: metaAttributeType objectclass:
> metaTop objectclass: top m-singleValue: TRUE m-oid:
> 1.3.6.1.4.1.1.0.4.3.2.1802 m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
> m-name: EndValidateDate : ERR_10026 Cannot add the AttributeType
> m-oid=1.3.6.1.4.1.1.0.4.3.2.1802, ou=attributeTypes, cn=schemaTAS, ou=schema, as
> the associated schema (schematas) is not loaded]
> dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1802, ou=attributeTypes, cn=schemaTAS, ou=sc
> hema
> objectclass: metaAttributeType
> objectclass: metaTop
> objectclass: top
> m-oid: 1.3.6.1.4.1.1.0.4.3.2.1802
> m-name: EndValidateDate
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
> m-singleValue: TRUE
Re: Custom Schemas and Partitions
Posted by dBug31 <ni...@free.fr>.
Yes sure, i'm sorry :)
I imported a schema (from an OpenLdap file) using Apache Schema Editor. My
schema is called "schemaTAS". I want now to use this news attributes and class
in my directory.
So i export the schema (Export>Schemas for Apache DS) my export looks like this :
----------------------------------------------------------------
# Generated by Apache Directory Studio on April 27, 2012 3:17:28 PM
# SCHEMA "SCHEMATAS"
dn: cn=schemaTAS, ou=schema
objectclass: metaSchema
objectclass: top
cn: schemaTAS
m-dependencies: system
m-dependencies: cosine
m-dependencies: inetorgperson
m-dependencies: core
dn: ou=attributeTypes, cn=schemaTAS, ou=schema
objectclass: organizationalUnit
objectclass: top
ou: attributetypes
dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1801, ou=attributeTypes, cn=schemaTAS, ou=schema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.1.0.4.3.2.1801
m-name: IpAddress
m-description: Adresse IP du serveur de l
m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
m-singleValue: TRUE
dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1802, ou=attributeTypes, cn=schemaTAS, ou=schema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.1.0.4.3.2.1802
m-name: EndValidateDate
m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
m-singleValue: TRUE
...
--------------------------------------------------------------------------
When i try to import this in the entry ou=schema i have this error log and
nothing in the ou=attributTypes nor ou=objectClasses...
--------------------------------------------------------------------------
# Generated by Apache Directory Studio on April 27, 2012 3:17:28 PM
# SCHEMA "SCHEMATAS"
#!RESULT OK
#!CONNECTION ldap://localhost:10389
#!DATE 2012-04-27T15:19:30.961
dn: cn=schemaTAS, ou=schema
objectclass: metaSchema
objectclass: top
cn: schemaTAS
m-dependencies: system
m-dependencies: cosine
m-dependencies: inetorgperson
m-dependencies: core
#!RESULT OK
#!CONNECTION ldap://localhost:10389
#!DATE 2012-04-27T15:19:31.021
dn: ou=attributeTypes, cn=schemaTAS, ou=schema
objectclass: organizationalUnit
objectclass: top
ou: attributetypes
#!RESULT ERROR
#!CONNECTION ldap://localhost:10389
#!DATE 2012-04-27T15:19:31.031
#!ERROR [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for Add Request
: ClientEntry dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1801, ou=attributeTypes,
cn=schemaTAS, ou=schema objectclass: metaAttributeType objectclass:
metaTop objectclass: top m-singleValue: TRUE m-oid:
1.3.6.1.4.1.1.0.4.3.2.1801 m-description: Adresse IP du serveur de l
m-syntax: 1.3.6.1.4.1.1466.115.121.1.15 m-name: IpAddress : ERR_10026 Cannot
add the AttributeType m-oid=1.3.6.1.4.1.1.0.4.3.2.1801, ou=attributeTypes,
cn=schemaTAS, ou=schema, as the associated schema (schematas) is not loaded]
dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1801, ou=attributeTypes, cn=schemaTAS, ou=sc
hema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.1.0.4.3.2.1801
m-name: IpAddress
m-description: Adresse IP du serveur de l
m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
m-singleValue: TRUE
#!RESULT ERROR
#!CONNECTION ldap://localhost:10389
#!DATE 2012-04-27T15:19:31.041
#!ERROR [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for Add Request
: ClientEntry dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1802, ou=attributeTypes,
cn=schemaTAS, ou=schema objectclass: metaAttributeType objectclass:
metaTop objectclass: top m-singleValue: TRUE m-oid:
1.3.6.1.4.1.1.0.4.3.2.1802 m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
m-name: EndValidateDate : ERR_10026 Cannot add the AttributeType
m-oid=1.3.6.1.4.1.1.0.4.3.2.1802, ou=attributeTypes, cn=schemaTAS, ou=schema, as
the associated schema (schematas) is not loaded]
dn: m-oid=1.3.6.1.4.1.1.0.4.3.2.1802, ou=attributeTypes, cn=schemaTAS, ou=sc
hema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.1.0.4.3.2.1802
m-name: EndValidateDate
m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
m-singleValue: TRUE
...
-------------------------------------------------------------------
the error i see and i don't undersand is "as the associated schema (schematas)
is not loaded"
Any ideas ?
Thanks
Re: Custom Schemas and Partitions
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Any other information you could share with us?
Like the exact problem (with files and/or logs) and how we could eventually reproduce it?
"Same problem" is pretty vague…
Regards,
Pierre-Arnaud
On 27 avr. 2012, at 15:38, dBug31 wrote:
> Hi, i have the same problem...
>
> Any help please ?
>