I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest with the -F and -f parameters with a specially crafted slapd.conf file.
As the person who is responsible for a *.schema file and develops it not on a machine that has the openldap server software installed, that process is not anything I'm interested in. Looks like it should be a fairly simple set of transformations. Looking at the *.schema and *.ldif that are provided with the openldap source - I am left wondering how they were created, since they have comments, they were obviously not created via the slaptest -F <x> -f <y> method.
I would like to programatically do this -- my ability to vi two files and make identical changes has been known to be fallable!
I found the fusiondirectory-schema2ldif perl script - but it is not complete and silently drops keywords it doesn't like which is a really nasty coding style generating garbage from quality schemas.
Suggestions? Code examples?
Thanks,
On Tue, Apr 3, 2012 at 9:28 AM, Francis Swasey Frank.Swasey@uvm.edu wrote:
I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest with the -F and -f parameters with a specially crafted slapd.conf file.
As the person who is responsible for a *.schema file and develops it not on a machine that has the openldap server software installed, that process is not anything I'm interested in. Looks like it should be a fairly simple set of transformations. Looking at the *.schema and *.ldif that are provided with the openldap source - I am left wondering how they were created, since they have comments, they were obviously not created via the slaptest -F <x> -f <y> method.
I would like to programatically do this -- my ability to vi two files and make identical changes has been known to be fallable!
I found the fusiondirectory-schema2ldif perl script - but it is not complete and silently drops keywords it doesn't like which is a really nasty coding style generating garbage from quality schemas.
Suggestions? Code examples?
I *believe* the reason you create the .conf file with all the schemas yours depend on is because it somehow needs to know its dependencies to continue.
Thanks,
-- Frank Swasey | http://www.uvm.edu/~fcs Sr Systems Administrator | Always remember: You are UNIQUE, University of Vermont | just like everyone else. "I am not young enough to know everything." - Oscar Wilde (1854-1900)
Francis Swasey wrote:
I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest with the -F and -f parameters with a specially crafted slapd.conf file.
As the person who is responsible for a *.schema file and develops it not on a machine that has the openldap server software installed, that process is not anything I'm interested in. Looks like it should be a fairly simple set of transformations. Looking at the *.schema and *.ldif that are provided with the openldap source - I am left wondering how they were created, since they have comments, they were obviously not created via the slaptest -F<x> -f<y> method.
I would like to programatically do this -- my ability to vi two files and make identical changes has been known to be fallable!
I found the fusiondirectory-schema2ldif perl script - but it is not complete and silently drops keywords it doesn't like which is a really nasty coding style generating garbage from quality schemas.
Suggestions? Code examples?
Read schema/openldap.ldif
On 4/3/12 11:50 AM, Howard Chu wrote:
I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest with the -F and -f parameters with a specially crafted slapd.conf file.
I would like to programatically do this -- my ability to vi two files and make identical changes has been known to be fallable!
Suggestions? Code examples?
Read schema/openldap.ldif
Thank you Howard. I didn't think to go looking for that kind of documentation.
If anyone is interested, I've thrown together a short perl script that does what schema/openldap.ldif suggests. I believe it will generate an ldif file that is just as valid as the schema file it is given ;-) I have tested that hypothesis via ldapadd on a system that I set up for cn=config use.
Le 03/04/12 20:39, Francis Swasey a écrit :
On 4/3/12 11:50 AM, Howard Chu wrote:
I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest with the -F and -f parameters with a specially crafted slapd.conf file.
I would like to programatically do this -- my ability to vi two files and make identical changes has been known to be fallable!
Suggestions? Code examples?
Read schema/openldap.ldif
Thank you Howard. I didn't think to go looking for that kind of documentation.
If anyone is interested, I've thrown together a short perl script that does what schema/openldap.ldif suggests. I believe it will generate an ldif file that is just as valid as the schema file it is given ;-) I have tested that hypothesis via ldapadd on a system that I set up for cn=config use.
I am indeed interested to see that script, if you'd be willing to share it?
Jonathan
Le 4/4/12 2:03 PM, Jonathan Clarke a écrit :
Le 03/04/12 20:39, Francis Swasey a écrit :
On 4/3/12 11:50 AM, Howard Chu wrote:
I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest with the -F and -f parameters with a specially crafted slapd.conf file.
I would like to programatically do this -- my ability to vi two files and make identical changes has been known to be fallable!
Suggestions? Code examples?
Read schema/openldap.ldif
Thank you Howard. I didn't think to go looking for that kind of documentation.
If anyone is interested, I've thrown together a short perl script that does what schema/openldap.ldif suggests. I believe it will generate an ldif file that is just as valid as the schema file it is given ;-) I have tested that hypothesis via ldapadd on a system that I set up for cn=config use.
I am indeed interested to see that script, if you'd be willing to share it?
Jonathan
FYI, I have created a JIRA in Apache Directory Studio to offer such a conversion, as it's quite easy to do (we already do that for ApacheDS, for instance) : https://issues.apache.org/jira/browse/DIRSTUDIO-800
It could be wipped in a couple of days, but that may not be added immediately.
openldap-technical@openldap.org
-
Emmanuel Lécharny -
Francis Swasey -
Howard Chu -
Jonathan Clarke -
Mauricio Tavares -
Nick Milas