#include <ldap.h>
#include <ldapssl.h>
LDAP *ldap_ssl_init(
char *host,
int port,
char *name)
|
The ldap_ssl_init() routine is used to initialize a secure SSL session with a server. Note that the server is not actually contacted until an operation is performed that requires it, allowing various options to be set after initialization. Once the secure connection is established for the ld, all subsequent LDAP messages that flow over the secure connection are encrypted, including the ldap_simple_bind() parameters, until ldap_unbind() is invoked.
Note that when connecting to an LDAP V2 server, one of the ldap_simple_bind() or ldap_bind() calls must be completed before other operations can be performed on the session (with the exception of ldap_set/get_option()). The LDAP V3 protocol does not require a bind operation before performing other operations.
Although still supported, the use of the ldap_ssl_start() API is now deprecated. The ldap_ssl_client_init() and ldap_ssl_init() APIs should be used instead.
No OS/400 authority is required. All authority checking is done by the LDAP server.
If the LDAP server is configured to perform Server Authentication, a client certificate is not required (and name can be set to null). If the LDAP server is configured to perform Client and Server Authentication, a client certificate is required. name can be set to null if a default certificate/private key pair has been designated as the default (using Using Ikmgui). Similarly, name can be set to null if there is a single certificate/private key pair in the designated key database.
The following scenario depicts the recommended calling sequence where the entire set of LDAP transactions are "protected" by using a secure SSL connection, including the dn and password that flow on the ldap_simple_bind():
rc = ldap_ssl_client_init (keyfile, keyfile_pw, timeout, reasoncode); ld = ldap_ssl_init(ldaphost, ldapport, label ); rc = ldap_set_option( ld, LDAP_OPT_SSL_CIPHER, &ciphers); rc = ldap_simple_bind_s(ld, binddn, passwd); ...additional LDAP API calls rc = ldap_unbind( ld );
Note that the sequence of calls for the deprecated APIs is ldap_open/init(), ldap_ssl_start(), followed by ldap_bind().
The following ciphers are attempted for the SSL handshake by default, in the order shown.
(Export Version) RC4_MD5_EXPORT RC2_MD5_EXPORT (Non-export Version) RC4_SHA_US RC4_MD5_US DES_SHA_US 3DES_SHA_US RC4_MD5_EXPORT RC2_MD5_EXPORT
See ldap_get/set_option() for more information on setting the ciphers to be used.
ldap_ssl_init() will return NULL and set the ld_errno error code, if not successful. See LDAP Client API Error Conditions for possible LDAP error codes values.
The following message may be set from this function.
CPF3CF2 E Error(s) occurred during running of ldap_ssl_init API.
ldap_ssl_client_init() -- Initializes the SSL library.
ldap_ssl_start() -- Creates a secure SSL connection (deprecated).
The ldap_ssl_init() API is only supported for the versions of the LDAP library that include the SSL component. It include RSA(1) software.
(1) RSA is a trademark of RSA Data Security, Inc.
|
Top
| LDAP APIs List APIs by category |
| [Information Center Home Page | Feedback ] | [Legal | AS/400 Glossary] |