1
edit
LDAP C SDK: Difference between revisions
→The Mozilla LDAP C SDK
| (15 intermediate revisions by 6 users not shown) | |||
| Line 2: | Line 2: | ||
Contact: Mark Smith <[mailto:mcs@pearlcrescent.com mcs@pearlcrescent.com]> | Contact: Mark Smith <[mailto:mcs@pearlcrescent.com mcs@pearlcrescent.com]> | ||
Discussion: [news://news.mozilla.org/mozilla.dev.tech.ldap mozilla.dev.tech.ldap] | Discussion: [news://news.mozilla.org/mozilla.dev.tech.ldap mozilla.dev.tech.ldap] | ||
===Latest News - 10/13/2017=== | |||
To my knowledge, the LDAP C SDK is no longer being actively developed. | |||
However, the LDAPJDK is still in use in various projects, and the source for all LDAP SDKS has been moved to the following URLS: | |||
* New Source Location: [https://github.com/dogtagpki/ldap-sdks https://github.com/dogtagpki/ldap-sdks] | |||
Additionally, all future issues with the LDAPJDK should be filed against the following URL (rather than the Mozilla Bugzilla LDAPJDK component): | |||
* New Ticket Location: [https://pagure.io/ldapjdk/ https://pagure.io/ldapjdk/] | |||
===Latest News - 1/31/2011=== | |||
Version 6.0.7 has been released! This version contains several bug fixes. [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=DirectorySDKSourceC&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-09-12+00%3A00%3A00&maxdate=2010-11-11+00%3A00%3A00&cvsroot=%2Fcvsroot Here] and [https://hg.mozilla.org/projects/ldap-sdks/pushloghtml?tochange=LDAPCSDK_6_0_7_RTM here] are the lists of changes made since 6.0.6 was released. The hg tags are LDAPCSDK_6_0_7_RTM and LDAPCSDK_20110106_607_RTM. The source tarball is here: ftp://ftp.mozilla.org/pub/mozilla.org/directory/c-sdk/releases/v6.0.7/src | |||
===Latest News - 12/1/2010=== | |||
The LDAP repositories have now moved to a [https://developer.mozilla.org/en/Mercurial Mercurial] [http://hg.mozilla.org/projects/ldap-sdks/ installation]. All development will now take place in that hg repository. | |||
There are two active branches: 'default' (equivalent to the old cvs HEAD), and 'devel-branch-1_4_2' a branch for perldap that was present in cvs. | |||
===Latest News - 6/3/2009=== | |||
Mozldap now supports the MozillaBuild environment for building on Windows platforms. The code is currently in CVS HEAD. | |||
More information about setting up the Windows environment is here - https://developer.mozilla.org/En/Developer_Guide/Build_Instructions/Windows_Prerequisites | |||
Here is the link to the MozillaBuild package - http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.3.exe | |||
===Latest News - 9/11/2008=== | |||
Version 6.0.6 has been released! This version contains several bug fixes. [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=DirectorySDKSourceC&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-01-03+00%3A00%3A00&maxdate=2008-09-11+00%3A00%3A00&cvsroot=%2Fcvsroot Here] is the list of changes made since 6.0.5 was released. The CVS tags are LDAPCSDK_6_0_6_RTM and LDAPCSDK_6_0_6_RTM_20080911. The source tarball is here: ftp://ftp.mozilla.org/pub/mozilla.org/directory/c-sdk/releases/v6.0.6/src | |||
===Latest News - 1/3/2008=== | |||
Version 6.0.5 has been released! This version contains several bug fixes. [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=DirectorySDKSourceC&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2007-07-05+00%3A00%3A00&maxdate=2008-01-03+00%3A00%3A00&cvsroot=%2Fcvsroot Here] is the list of changes made since 6.0.4 was released. The CVS tag is LDAPCSDK_6_0_5_RTM. The source tarball is here: ftp://ftp.mozilla.org/pub/mozilla.org/directory/c-sdk/releases/v6.0.5/src | |||
===Latest News - 7/5/2007=== | |||
Version 6.0.4 has been released! This version has support for using CMU SASL on Windows, and creating a Windows .zip package, as well as many bug fixes. [http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=DirectorySDKSourceC&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2007-03-09+00%3A00%3A00&maxdate=2007-07-05+00%3A00%3A00&cvsroot=%2Fcvsroot Here] is the list of changes made since 6.0.3 was released. The CVS tags are LDAPCSDK_6_0_4_RTM and LDAPCSDK_20070705_604_RTM. The source tarball is here: ftp://ftp.mozilla.org/pub/mozilla.org/directory/c-sdk/releases/v6.0.4/src | |||
Sun has released their updated SDK documentation. This is now in mozilla CVS under mozilla/directory/docs. These are in DocBook 4.3 XML format. | |||
===Latest News - 3/13/2007=== | ===Latest News - 3/13/2007=== | ||
| Line 43: | Line 81: | ||
# Get the CVS client and set your computer up mozilla work. [http://www.mozilla.org/cvs.html Read through the instructions] on using CVS. Make sure you have set your CVSROOT environment variable and that you have successfully executed the cvs login command. | # Get the CVS client and set your computer up mozilla work. [http://www.mozilla.org/cvs.html Read through the instructions] on using CVS. Make sure you have set your CVSROOT environment variable and that you have successfully executed the cvs login command. | ||
# Pull the current LDAP C SDK code (which is located on the CVS trunk) using this command: cvs co -P [-r currentrelease] DirectorySDKSourceC The most current release is | # Pull the current LDAP C SDK code (which is located on the CVS trunk) using this command: cvs co -P [-r currentrelease] DirectorySDKSourceC The most current release is LDAPCSDK_6_0_6_RTM, so to pull this version (recommended), use this command: cvs co -P -r LDAPCSDK_6_0_6_RTM DirectorySDKSourceC | ||
# Pull the code for libraries that LDAP C SDK depends on. Pull [http://www.mozilla.org/projects/nspr/ NSPR] and [http://www.mozilla.org/projects/security/pki/nss/ NSS] using these commands: | # Pull the code for libraries that LDAP C SDK depends on. Pull [http://www.mozilla.org/projects/nspr/ NSPR] and [http://www.mozilla.org/projects/security/pki/nss/ NSS] using these commands: | ||
cvs co | cvs co mozilla/nsprpub | ||
cvs co | cvs co mozilla/security/coreconf mozilla/security/nss mozilla/security/dbm mozilla/dbm | ||
There is an optional package called SVRCORE which provides secure PIN management for the command line and Windows clients. This is recommended for using the command line tools with SSL, for a more secure environment. | There is an optional package called SVRCORE which provides secure PIN management for the command line and Windows clients. This is recommended for using the command line tools with SSL, for a more secure environment. | ||
cvs co | cvs co mozilla/security/svrcore [mozilla/security/coreconf] | ||
Add mozilla/security/coreconf on Windows only. Alternatively, you can [ftp://ftp.mozilla.org/pub/mozilla.org/nspr/releases/ download stable binary releases of NSPR] and [ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/ NSS] and drop them into your source tree under mozilla/dist. See ftp://ftp.mozilla.org/pub/mozilla.org/nspr/releases/ for NSPR releases and ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/ for NSS releases. | Add mozilla/security/coreconf on Windows only. Alternatively, you can [ftp://ftp.mozilla.org/pub/mozilla.org/nspr/releases/ download stable binary releases of NSPR] and [ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/ NSS] and drop them into your source tree under mozilla/dist. See ftp://ftp.mozilla.org/pub/mozilla.org/nspr/releases/ for NSPR releases and ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/ for NSS releases. | ||
| Line 59: | Line 97: | ||
Follow these instructions to obtain the necessary build tools: | Follow these instructions to obtain the necessary build tools: | ||
* [http:// | * [http://developer.mozilla.org/en/Windows_Build_Prerequisites Microsoft Windows] | ||
* | ** Note: CVS HEAD can now use MozillaBuild which is based on msys | ||
** Latest MozillaBuild - http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-1.3.exe | |||
* [http://developer.mozilla.org/en/Linux_Build_Prerequisites Linux and Unix] | |||
Follow these instructions to set up your environment: | Follow these instructions to set up your environment: | ||
* [http://www.mozilla.org/build/win32.html#software Microsoft Windows] - Note that MOZCONFIG is not used for LDAP C SDK builds, so it is safe to leave it unset. | * [http://www.mozilla.org/build/win32.html#software Microsoft Windows] | ||
** If building LDAP C SDK 6.0.5 or older, follow the instructions below - they do not apply if using MozillaBuild with msys, they assume the use of cygwin | |||
** Note that MOZCONFIG is not used for LDAP C SDK builds, so it is safe to leave it unset. | |||
** Also note that the only mozilla build program you should use is nsinstall.exe - DO NOT USE THE OTHER TOOLS TO BUILD THE STANDALONE LDAP C SDK - just put nsinstall.exe somewhere in your PATH | |||
** If you get strange errors from link, you may have to remove the cygwin "link" command | |||
* Solaris using GCC (instead of the Sun/Forte compiler) | * Solaris using GCC (instead of the Sun/Forte compiler) | ||
** Requires GCC 3.4 or later | ** Requires GCC 3.4 or later | ||
| Line 82: | Line 126: | ||
./configure [--with-nspr=/path] [--with-nss=/path] | ./configure [--with-nspr=/path] [--with-nss=/path] | ||
make [USE_64=1] | make [USE_64=1] | ||
Note that since svrcore requires NSS, --with-svrcore implies --with-nss | |||
* Read the [http://www.mozilla.org/projects/security/pki/nss/nss-3.9/nss-3.9-build.html NSS Build Instructions] and the [http://www.mozilla.org/projects/nspr/eng-process/build.html NSPR Build Instructions] if you run into problems. Note that the instructions for NSS say to use the NSS_3_9_RTM tag to pull the source, but use NSS_3_11_4_RTM instead. Build the LDAP C SDK libraries: | * Read the [http://www.mozilla.org/projects/security/pki/nss/nss-3.9/nss-3.9-build.html NSS Build Instructions] and the [http://www.mozilla.org/projects/nspr/eng-process/build.html NSPR Build Instructions] if you run into problems. Note that the instructions for NSS say to use the NSS_3_9_RTM tag to pull the source, but use NSS_3_11_4_RTM instead. Build the LDAP C SDK libraries: | ||
cd mozilla/directory/c-sdk | cd mozilla/directory/c-sdk | ||
| Line 95: | Line 140: | ||
make | make | ||
* Build with SASL support: | * Build with SASL support: | ||
:::SASL support requires Cyrus SASL or vendor compatible implementation available on the target system. some OS ship with SASL library and plug-ins at standard locations, for instance on Solaris 10 and Linux all you have to do is to specify --with-sasl so autoconf will look for it in all the standard locations. for any OS that does not ship SASL as part of its distribution you might wanna check if there are any SASL packages available separately either by OS vendor or trusted third party and if none available you can build Cyrus SASL from the source which also can be a preferred option in cases when you require certain SASL library or plug-ins customization to suit your needs. | |||
:::information on obtaining Cyrus SASL source can be found at http://asg.web.cmu.edu/sasl/sasl-library.html | |||
:::information on building, using and troubleshooting Cyrus SASL is included within its source distribution. | |||
:::at the time of this writing cyrus-sasl-2.1.22 is the latest version available and can be build using the following options: | |||
cd cyrus-sasl-2.1.22 | |||
./configure --enable-gssapi --without-des --without-openssl --without-saslauthd \ | |||
--disable-ldapdb --with-dblib=none --prefix=DIR --enable-shared \ | |||
--disable-static | |||
:::where prefix option will vary to fit your own installation path. --with-plugindir=DIR option can be used if you do not plan to install SASL plug-ins at default location [/usr/lib/sasl2], otherwise SASL_PATH environment variable can be used by Cyrus SASL at runtime to determine the location of its plug-ins. | |||
:::also note that default set of plug-ins will vary depending on platform. LDAP C SDK does not require any plug-ins in order to be build with SASL support however you need to make sure that specific plug-ins for SASL mechanisms you will use at runtime are available at the plug-in location. | |||
:::Cyrus SASL libraries and headers installed at standard location/s: | |||
cd mozilla/directory/c-sdk | cd mozilla/directory/c-sdk | ||
./configure ...other options above... --with-sasl | ./configure ...other options above... --with-sasl | ||
:::OR Cyrus SASL libraries and headers installed at non standard location/s: | |||
cd mozilla/directory/c-sdk | |||
./configure ...other options above... --with-sasl-inc=DIR/include/sasl --with-sasl-lib=DIR/lib | |||
====Building Cyrus SASL on Windows==== | |||
Building Cyrus SASL on Windows requires some special instrctions - see [[LDAP_C_SDK_SASL_Windows]] for more information and required patches. | |||
If your build is successful, the LDAP C SDK libraries, command line tools, and header files will be placed under mozilla/dist/<OSNAME>.OBJ/. | If your build is successful, the LDAP C SDK libraries, command line tools, and header files will be placed under mozilla/dist/<OSNAME>.OBJ/. | ||