Hi,
I see a few references of building OpenLDAP in Windows using MSVC6 - but I don't see any updated and comprehensive document. Can somebody help?
Regds,
Rajarshi Chaudhuri Genesys Telecommunications Lab, Inc rajarshi@genesyslab.com mailto:rajarshi@genesyslab.com
Rajarshi Chaudhuri wrote:
Hi,
I see a few references of building OpenLDAP in Windowsusing MSVC6 – but I don’t see any updated and comprehensive document. Can somebody help?
Use MSYS and cccl. The general info for using MSYS is here http://www.openldap.org/faq/data/cache/300.html
Ignore the old information about untested features. The entire suite builds and runs fine.
And of course, Symas provides pre-built and tested packages of CDS for Windows.
Thanks Howard. I have also sent a mail to Symas sales for licensing price info for CDS packages for Windows.
One follow up question - is there a way to turn off schema checking in OpenLDAP 2.3? Is it possible in CDS distributed by Symas?
Rajarshi Chaudhuri Genesys Telecommunications Lab, Inc rajarshi@genesyslab.com
-----Original Message----- From: Howard Chu [mailto:hyc@symas.com] Sent: Tuesday, February 13, 2007 4:36 PM To: Rajarshi Chaudhuri Cc: openldap-software@openldap.org Subject: Re: Building OpenLDAP with MSVC 6
Rajarshi Chaudhuri wrote:
Hi,
I see a few references of building OpenLDAP in Windows
using MSVC6 - but I don't see any updated and comprehensive document. Can somebody help?
Use MSYS and cccl. The general info for using MSYS is here http://www.openldap.org/faq/data/cache/300.html
Ignore the old information about untested features. The entire suite builds and runs fine.
And of course, Symas provides pre-built and tested packages of CDS for Windows.
Rajarshi Chaudhuri wrote:
Thanks Howard. I have also sent a mail to Symas sales for licensing price info for CDS packages for Windows.
One follow up question - is there a way to turn off schema checking in OpenLDAP 2.3? Is it possible in CDS distributed by Symas?
No. Schema is an integral part of the LDAPv3 specification; schema checking cannot be disabled. Why do you want to turn it off?
Rajarshi Chaudhuri Genesys Telecommunications Lab, Inc rajarshi@genesyslab.com
Howard Chu wrote:
Rajarshi Chaudhuri wrote:
Thanks Howard. I have also sent a mail to Symas sales for licensing price info for CDS packages for Windows.
One follow up question - is there a way to turn off schema checking in OpenLDAP 2.3? Is it possible in CDS distributed by Symas?
No. Schema is an integral part of the LDAPv3 specification; schema checking cannot be disabled. Why do you want to turn it off?
I realize the schema being published in the DIT is an integral part of the v3 spec (schema checking is something that could have been in v2 though as far as I would guess) however I know that other LDAP implementations do allow it to be turned off so he had a good question.
On Tue, 13 Feb 2007, Brandon McCombs wrote:
No. Schema is an integral part of the LDAPv3 specification; schema checking cannot be disabled. Why do you want to turn it off?
I realize the schema being published in the DIT is an integral part of the v3 spec (schema checking is something that could have been in v2 though as far as I would guess) however I know that other LDAP implementations do allow it to be turned off so he had a good question.
It's still a silly idea; fix the data to comply with the schema, not the other way around.
Brandon McCombs wrote:
Howard Chu wrote:
Rajarshi Chaudhuri wrote:
Thanks Howard. I have also sent a mail to Symas sales for licensing price info for CDS packages for Windows.
One follow up question - is there a way to turn off schema checking in OpenLDAP 2.3? Is it possible in CDS distributed by Symas?
No. Schema is an integral part of the LDAPv3 specification; schema checking cannot be disabled. Why do you want to turn it off?
I realize the schema being published in the DIT is an integral part of the v3 spec (schema checking is something that could have been in v2 though as far as I would guess) however I know that other LDAP implementations do allow it to be turned off so he had a good question.
The question begs the other question though - what one is actually trying to accomplish. There isn't enough context to tell. That's why I asked for clarification.
"Other LDAP implementations that don't do schema checking" is an oxymoron - those are not LDAP implementations. They implement some bizarre vendor-specific non-standard undocumented protocol that sort of looks like LDAP until you actually try to use and interoperate with it. That may be many things, but LDAP it's not.
Howard Chu wrote:
Brandon McCombs wrote:
Howard Chu wrote:
Rajarshi Chaudhuri wrote:
Thanks Howard. I have also sent a mail to Symas sales for licensing price info for CDS packages for Windows.
One follow up question - is there a way to turn off schema checking in OpenLDAP 2.3? Is it possible in CDS distributed by Symas?
No. Schema is an integral part of the LDAPv3 specification; schema checking cannot be disabled. Why do you want to turn it off?
I realize the schema being published in the DIT is an integral part of the v3 spec (schema checking is something that could have been in v2 though as far as I would guess) however I know that other LDAP implementations do allow it to be turned off so he had a good question.
The question begs the other question though - what one is actually trying to accomplish. There isn't enough context to tell. That's why I asked for clarification.
"Other LDAP implementations that don't do schema checking" is an oxymoron - those are not LDAP implementations. They implement some bizarre vendor-specific non-standard undocumented protocol that sort of looks like LDAP until you actually try to use and interoperate with it. That may be many things, but LDAP it's not.
Well maybe OpenLDAP is the only one and thus the exception but I don't know of any LDAP implementation that doesn't have it's own little twist on the standard. The one implementation I alluded to provides the *option* to disable schema checking; by default it is on unless an administrator disables it during installation. After building a Java-based LDAP client that can communicate with 3 different directory servers I can attest to the fact that at least any 2 of them (if not all 3 in some respects) would behave differently in one way or another. It would be nice if they all conformed to the standard but when implemented by commercial entities they all want to put their own twist on the product to differentiate themselves.
Brandon McCombs wrote:
Howard Chu wrote:
"Other LDAP implementations that don't do schema checking" is an oxymoron - those are not LDAP implementations. They implement some bizarre vendor-specific non-standard undocumented protocol that sort of looks like LDAP until you actually try to use and interoperate with it. That may be many things, but LDAP it's not.
Well maybe OpenLDAP is the only one and thus the exception but I don't know of any LDAP implementation that doesn't have it's own little twist on the standard. The one implementation I alluded to provides the *option* to disable schema checking; by default it is on unless an administrator disables it during installation. After building a Java-based LDAP client that can communicate with 3 different directory servers I can attest to the fact that at least any 2 of them (if not all 3 in some respects) would behave differently in one way or another. It would be nice if they all conformed to the standard but when implemented by commercial entities they all want to put their own twist on the product to differentiate themselves.
Since LDAP is an extensible protocol, there's nothing wrong with different vendors adding new features to their products to differentiate themselves. But those are extensions, and here we're talking about the base, core specification. If they don't implement the core specification then they're not implementing "LDAP".
Extensions can do many things, but they all have to be explicitly requested by the client. They can change the server behavior but their use is supposed to be optional; a server cannot unilaterally impose non-standard behaviors on unwitting clients. And no matter what the extension does, ultimately the contents of the DIT must still conform to the X.500 data model.
When you accept non-standard behaviors in the core implementation of a server, you've implicitly agreed to be locked in to that version of the product (not just that *vendor*...). One need only look at Microsoft's embrace/extend/extinguish practices to see where that will lead you.
The purpose of a standard is to establish a known reference point, so that any basic client can get consistent service from any unknown server. When vendors cut corners and omit elements of the basic specification, you really need to ask yourself what else did they fail to do correctly? What other technical integrity did they sacrifice for the sake of expedience, and in what least-convenient moment are you going to discover it firsthand?
On that score, when a vendor like Sun tosses up their hands and says "our JSDS code base is unmaintainable, let's start over" that speaks volumes about the other questions. https://opends.dev.java.net/public/docs/OpenDS-FAQ.html#why_not_os_sjsds
I would add to Howard's reply that at least OpenLDAP is committed to wipe out any inconsistency with LDAPv3 specifications that anyone may find in its code, while rejecting any request to introduce such inconsistencies. I don't know how many vendors can claim the same. In most cases they simply lost the capability to maintain their code.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati@sys-net.it ------------------------------------------
Howard -
We used Sun ONE before - and there is no restriction on schema - so we have put some flexibility in our components that register with ldap. Now, with OpenLDAP since the schema is fixed - that flexibility is lost; if we update any component template (the data that goes into schema) - then we need to re-generate the schema before re-installing the new version of the component.
So - that's the reason why I'm asking this question - if this restriction can be somehow bypassed.
- Rajarshi
________________________________
From: Howard Chu [mailto:hyc@symas.com] Sent: Tue 2/13/2007 8:10 PM To: Rajarshi Chaudhuri Cc: openldap-software@openldap.org Subject: Re: Building OpenLDAP with MSVC 6
Rajarshi Chaudhuri wrote:
Thanks Howard. I have also sent a mail to Symas sales for licensing price info for CDS packages for Windows.
One follow up question - is there a way to turn off schema checking in OpenLDAP 2.3? Is it possible in CDS distributed by Symas?
No. Schema is an integral part of the LDAPv3 specification; schema checking cannot be disabled. Why do you want to turn it off?
Rajarshi Chaudhuri Genesys Telecommunications Lab, Inc rajarshi@genesyslab.com
-- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc Chief Architect, OpenLDAP http://www.openldap.org/project/
Rajarshi Chaudhuri wrote:
Howard -
We used Sun ONE before - and there is no restriction on schema - so we have put some flexibility in our components that register with ldap. Now, with OpenLDAP since the schema is fixed - that flexibility is lost; if we update any component template (the data that goes into schema) - then we need to re-generate the schema before re-installing the new version of the component.
So - that's the reason why I'm asking this question - if this restriction can be somehow bypassed.
It should be clear from the other replies here that such a goal is the wrong approach.
You should simply update your schema whenever you make changes to your templates. With OpenLDAP 2.3 you can add new schema elements on the fly. With OpenLDAP 2.4 you can add/delete/modify schema at will.
- Rajarshi
From: Howard Chu [mailto:hyc@symas.com] Sent: Tue 2/13/2007 8:10 PM To: Rajarshi Chaudhuri Cc: openldap-software@openldap.org Subject: Re: Building OpenLDAP with MSVC 6
Rajarshi Chaudhuri wrote:
Thanks Howard. I have also sent a mail to Symas sales for licensing price info for CDS packages for Windows.
One follow up question - is there a way to turn off schema checking in OpenLDAP 2.3? Is it possible in CDS distributed by Symas?
No. Schema is an integral part of the LDAPv3 specification; schema checking cannot be disabled. Why do you want to turn it off?
Rajarshi Chaudhuri Genesys Telecommunications Lab, Inc rajarshi@genesyslab.com
Howard -
Thanks for your response. Yes we are updating our side to add new schema elements on the fly (openldap 2.3). Openldap 2.4 seems to be more flexible - but I guess it's not stable release yet.
- Rajarshi
________________________________
From: Howard Chu [mailto:hyc@symas.com] Sent: Wed 2/14/2007 12:14 AM To: Rajarshi Chaudhuri Cc: openldap-software@openldap.org Subject: Re: Building OpenLDAP with MSVC 6
Rajarshi Chaudhuri wrote:
Howard -
We used Sun ONE before - and there is no restriction on schema - so we have put some flexibility in our components that register with ldap. Now, with OpenLDAP since the schema is fixed - that flexibility is lost; if we update any component template (the data that goes into schema) - then we need to re-generate the schema before re-installing the new version of the component.
So - that's the reason why I'm asking this question - if this restriction can be somehow bypassed.
It should be clear from the other replies here that such a goal is the wrong approach.
You should simply update your schema whenever you make changes to your templates. With OpenLDAP 2.3 you can add new schema elements on the fly. With OpenLDAP 2.4 you can add/delete/modify schema at will.
- Rajarshi
From: Howard Chu [mailto:hyc@symas.com] Sent: Tue 2/13/2007 8:10 PM To: Rajarshi Chaudhuri Cc: openldap-software@openldap.org Subject: Re: Building OpenLDAP with MSVC 6
Rajarshi Chaudhuri wrote:
Thanks Howard. I have also sent a mail to Symas sales for licensing price info for CDS packages for Windows.
One follow up question - is there a way to turn off schema checking in OpenLDAP 2.3? Is it possible in CDS distributed by Symas?
No. Schema is an integral part of the LDAPv3 specification; schema checking cannot be disabled. Why do you want to turn it off?
Rajarshi Chaudhuri Genesys Telecommunications Lab, Inc rajarshi@genesyslab.com
-- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc Chief Architect, OpenLDAP http://www.openldap.org/project/
openldap-software@openldap.org
-
Brandon McCombs -
Dave Horsfall -
Howard Chu -
Pierangelo Masarati -
Rajarshi Chaudhuri