/netbsd-src/external/bsd/openldap/dist/doc/rfc/ |
H A D | INDEX | 4 rfc2247.txt Using Domains in LDAP DNs (PS) 7 rfc2307.txt LDAP Network Information Services Schema (E) 8 rfc2377.txt LDAP Naming Plan (I) 11 rfc2696.txt LDAP Simple Paged Result Control (I) 12 rfc2713.txt LDAP Java schema (I) 13 rfc2714.txt LDAP CORBA schema (I) 14 rfc2798.txt LDAP inetOrgPerson schema (I) 17 rfc2926.txt LDAP: Conversion of LDAP Schemas to and from SLP Templates (I) 18 rfc3045.txt Storing Vendor Information in the LDAP root DSE (I) 19 rfc3062.txt LDAP Password Modify Extended Operation (PS) [all …]
|
H A D | rfc4510.txt | 14 Lightweight Directory Access Protocol (LDAP): 31 The Lightweight Directory Access Protocol (LDAP) is an Internet 34 provides a road map of the LDAP Technical Specification. 36 1. The LDAP Technical Specification 39 Directory Access Protocol (LDAP), an Internet Protocol, consists of 42 LDAP: The Protocol [RFC4511] 43 LDAP: Directory Information Models [RFC4512] 44 LDAP: Authentication Methods and Security Mechanisms [RFC4513] 45 LDAP: String Representation of Distinguished Names [RFC4514] 46 LDAP: String Representation of Search Filters [RFC4515] [all …]
|
H A D | rfc4516.txt | 14 Lightweight Directory Access Protocol (LDAP): 32 Protocol (LDAP) Uniform Resource Locator (URL). An LDAP URL 33 describes an LDAP search operation that is used to retrieve 34 information from an LDAP directory, or, in the context of an LDAP 35 referral or reference, an LDAP URL describes a service where an LDAP 43 3. Defaults for Fields of the LDAP URL .............................5 60 RFC 4516 LDAP: Uniform Resource Locator June 2006 65 LDAP is the Lightweight Directory Access Protocol [RFC4510]. This 66 document specifies the LDAP URL format for version 3 of LDAP and 67 clarifies how LDAP URLs are resolved. This document also defines an [all …]
|
H A D | rfc4525.txt | 12 Lightweight Directory Access Protocol (LDAP) 29 Access Protocol (LDAP) Modify operation to support an increment 42 5.2. LDAP Protocol Mechanism ....................................3 43 5.3. LDAP Protocol Mechanism ....................................4 50 The Lightweight Directory Access Protocol (LDAP) [RFC4510] does not 60 RFC 4525 LDAP Modify-Increment Extension June 2006 67 This document extends the LDAP Modify Operation [RFC4511] to support 69 with either the LDAP pre-read or post-read control extensions 70 [RFC4527]. This feature may also be used with the LDAP assertion 80 This document extends the LDAP Modify request to support a increment [all …]
|
H A D | rfc2649.txt | 12 An LDAP Control and Schema for Holding Operation Signatures 29 document describes an LDAP message control which allows for the 31 LDAP v3 based mechanism for signing directory operations in order to 35 entries" is also defined. This document specifies LDAP v3 controls 36 that enable this functionality. It also defines an LDAP v3 schema 60 RFC 2649 LDAP Control and Schema August 1999 67 document describes an LDAP message control which allows for the 69 document is that the origin of the information that is stored in LDAP 70 v3 accessible directories is the LDAP v3 client that creates the 74 of an individual LDAP connection can be guaranteed by making use of [all …]
|
H A D | rfc4520.txt | 15 the Lightweight Directory Access Protocol (LDAP) 30 of the Lightweight Directory Access Protocol (LDAP). The document 36 The Lightweight Directory Access Protocol [RFC4510] (LDAP) is an 37 extensible protocol. LDAP supports: 47 - LDAP message types 48 - LDAP extended operations and controls 49 - LDAP result codes 50 - LDAP authentication methods 51 - LDAP attribute description options 60 RFC 4520 IANA Considerations for LDAP June 2006 [all …]
|
H A D | rfc4521.txt | 14 Lightweight Directory Access Protocol (LDAP) Extensions 28 The Lightweight Directory Access Protocol (LDAP) is extensible. It 31 discusses considerations for designers of LDAP extensions. 60 RFC 4521 LDAP Extensions June 2006 76 3. LDAP Operation Extensions .......................................6 86 4. Extending the LDAP ASN.1 Definition .............................9 88 4.2. LDAP Message Types .........................................9 92 5.1. LDAP Syntaxes .............................................11 99 6.3. LDAP URL Extensions .......................................12 116 RFC 4521 LDAP Extensions June 2006 [all …]
|
H A D | rfc4373.txt | 14 Lightweight Directory Access Protocol (LDAP) 29 The Lightweight Directory Access Protocol (LDAP) Bulk 30 Update/Replication Protocol (LBURP) allows an LDAP client to perform 31 a bulk update to an LDAP server. The protocol frames a sequenced set 32 of update operations within a pair of LDAP extended operations to 41 updates to the entries in an LDAP server. 60 RFC 4373 LDAP Bulk Update/Replication Protocol January 2006 94 9.1. LDAP Object Identifier Registrations ......................13 116 RFC 4373 LDAP Bulk Update/Replication Protocol January 2006 121 The Lightweight Directory Access Protocol (LDAP) Bulk [all …]
|
H A D | rfc2926.txt | 16 Conversion of LDAP Schemas to and from SLP Templates 32 directory access protocol (LDAP) descriptions of services. The 34 between SLP service type templates and LDAP directory schema. 36 mapping from service type templates to LDAP types is straightforward. 41 representation of service information in an LDAP directory. The 43 allowing SLP directory agents to backend into LDAP directory servers. 45 easily between SLP and LDAP. 60 RFC 2926 Conversion of LDAP Schemas September 2000 66 2.0 Mapping SLP Templates to LDAP Schema ........................ 3 67 2.1 Mapping from SLP Attribute Types to LDAP Attribute Types .. 8 [all …]
|
H A D | rfc4527.txt | 12 Lightweight Directory Access Protocol (LDAP) 31 Access Protocol (LDAP) to allow the client to read the target entry 47 6.2. LDAP Protocol Mechanisms ...................................5 60 RFC 4527 LDAP Read Entry Controls June 2006 66 Access Protocol (LDAP) [RFC4510] to allow the client to read the 116 RFC 4527 LDAP Read Entry Controls June 2006 128 The Pre-Read request control is a LDAP Control [RFC4511] whose 132 the modifyRequest, delRequest, and modDNRequest LDAP messages. 134 The corresponding response control is a LDAP Control whose 138 modifyResponse, delResponse, and modDNResponse LDAP messages with a [all …]
|
H A D | rfc4517.txt | 14 Lightweight Directory Access Protocol (LDAP): 33 (LDAP) directory, whose values may be transferred in the LDAP 40 defining attributes for LDAP directories. 60 RFC 4517 LDAP: Syntaxes and Matching Rules June 2006 75 3.3.18. LDAP Syntax Description ...........................16 116 RFC 4517 LDAP: Syntaxes and Matching Rules June 2006 147 (LDAP) directory [RFC4510], whose values may be transferred in the 148 LDAP protocol [RFC4511], has a defined syntax (i.e., data type) that 155 LDAP directories. 159 document. Section 3 provides definitions for the base set of LDAP [all …]
|
H A D | rfc4530.txt | 12 Lightweight Directory Access Protocol (LDAP) 30 This document describes the LDAP/X.500 'entryUUID' operational 60 RFC 4530 LDAP entryUUID June 2006 86 the Lightweight Directory Access Protocol (LDAP) [RFC4510], an object 104 Schema definitions are provided using LDAP description formats 116 RFC 4530 LDAP entryUUID June 2006 135 In LDAP, UUID values are encoded using the [ASCII] character string 139 The following is an LDAP syntax description suitable for publication 153 The following is an LDAP matching rule description suitable for 172 RFC 4530 LDAP entryUUID June 2006 [all …]
|
H A D | rfc4531.txt | 12 Lightweight Directory Access Protocol (LDAP) 30 (LDAP) extended operation to reverse (or "turn") the roles of client 50 6.2. LDAP Protocol Mechanism ....................................7 60 RFC 4531 LDAP Turn Operation June 2006 65 The Lightweight Directory Access Protocol (LDAP) [RFC4510][RFC4511] 73 specification detailing how to implement server-initiated LDAP 75 other security mechanisms to support server-initiated LDAP sessions. 84 directory servers that desire to request, as LDAP clients, that 102 The Turn operation is defined as an LDAP-Extended Operation 116 RFC 4531 LDAP Turn Operation June 2006 [all …]
|
/netbsd-src/external/gpl3/gcc/dist/libphobos/libdruntime/core/sys/windows/ |
H A D | winldap.d | 283 struct LDAP { 301 alias LDAP* PLDAP; 465 int ldap_perror(LDAP* handle, char* message) { 479 ULONG ldap_connect(LDAP*, LDAP_TIMEVAL*); 482 ULONG ldap_start_tls_sA(LDAP*, PLDAPControlA*, PLDAPControlA*); 483 ULONG ldap_start_tls_sW(LDAP*, PLDAPControlW*, PLDAPControlW*); 484 BOOLEAN ldap_stop_tls_s(LDAP*); 485 ULONG ldap_get_optionA(LDAP*, int, void*); 486 ULONG ldap_get_optionW(LDAP*, int, void*); 487 ULONG ldap_set_optionA(LDAP*, int, void*); [all …]
|
/netbsd-src/external/bsd/openldap/dist/include/ |
H A D | ldap.h | 799 typedef struct ldap LDAP; typedef 949 LDAP *ls_ld; 981 typedef int (ldap_conn_add_f) LDAP_P(( LDAP *ld, Sockbuf *sb, LDAPURLDesc *srv, struct sockaddr *ad… 984 typedef void (ldap_conn_del_f) LDAP_P(( LDAP *ld, Sockbuf *sb, struct ldap_conncb *ctx )); 1006 LDAP *ld, 1012 LDAP *ld, 1018 LDAP *ld, LDAP_CONST char *url, 1024 LDAP *ld, 1030 LDAP *ld, char ***refsp, int *cntp, 1035 LDAP *ld, [all …]
|
/netbsd-src/external/bsd/openldap/dist/libraries/libldap/ |
H A D | ldap-int.h | 600 LDAP *ld, 619 LDAP *ld, 632 LDAP *ld, 643 LDAP *ld, 688 LDAP *ld, 700 LDAP *ld, 718 LDAP_F (int) ldap_log_printf LDAP_P((LDAP *ld, int level, const char *fmt, ...)) LDAP_GCCATTR((form… 724 LDAP *ld, 729 LDAP *ld, 741 LDAP_F (int) ldap_open_defconn( LDAP *ld ); [all …]
|
H A D | open.c | 45 int ldap_open_defconn( LDAP *ld ) in ldap_open_defconn() 68 ldap_connect( LDAP *ld ) in ldap_connect() 92 LDAP * 96 LDAP *ld; in ldap_open() 124 ldap_create( LDAP **ldp ) in ldap_create() 126 LDAP *ld; in ldap_create() 144 if ( (ld = (LDAP *) LDAP_CALLOC( 1, sizeof(LDAP) )) == NULL ) { in ldap_create() 274 LDAP * 277 LDAP *ld; in ldap_init() 300 ldap_initialize( LDAP **ldp, LDAP_CONST char *url ) in ldap_initialize() [all …]
|
/netbsd-src/external/bsd/openldap/dist/doc/drafts/ |
H A D | draft-sermersheim-ldap-csn-xx.txt | 12 The LDAP Change Sequence Number 47 Directory Access Protocol (LDAP) which is used to hold a Change 50 It may be used by various attributes for various LDAP replication, 58 Internet-Draft LDAP CSN February 2005 64 LDAP Extensions mailing list <ldapext@ietf.org>. Please send 85 A.1. LDAP Object Identifier Registrations . . . . . . . . . 11 86 A.2. LDAP Descriptor Registrations . . . . . . . . . . . . 11 114 Internet-Draft LDAP CSN February 2005 170 Internet-Draft LDAP CSN February 2005 226 Internet-Draft LDAP CSN February 2005 [all …]
|
H A D | draft-ietf-ldapext-ldap-c-api-xx.txt | 17 The C LDAP Application Program Interface 42 cussion of this document will take place on the IETF LDAP Extension 56 C LDAP API C LDAP Application Program Interface 17 November 2000 62 to the Lightweight Directory Access Protocol (LDAP). This document 65 LDAP protocol. New extended operation functions were added to support 66 LDAPv3 features such as controls. In addition, other LDAP API changes 73 The C LDAP API is designed to be powerful, yet simple to use. It defines 74 compatible synchronous and asynchronous interfaces to LDAP to suit a 76 the LDAP model, then an overview of how the API is used by an applica- 77 tion program to obtain LDAP information. The API calls are described in [all …]
|
H A D | draft-sermersheim-ldap-subordinate-scope-xx.txt | 8 Subordinate Subtree Search Scope for LDAP 44 The Lightweight Directory Application Protocol (LDAP) specification 56 Internet-Draft Subordinate Subtree Search Scope for LDAP July 2004 60 LDAP Extensions mailing list <ldapext@ietf.org>. Please send 66 Lightweight Directory Application Protocol (LDAP) [RFC3377] 70 obvious utility of allowing an LDAP client application the ability to 81 LDAP URL [RFC2255] and may be applied to other specifications which 82 include an LDAP search scope. A mechanism is also given which allows 83 LDAP Directory Server Agents (DSA)s to advertise support of this 99 3. LDAP URL applications [all …]
|
H A D | draft-wahl-ldap-session-xx.txt | 10 LDAP Session Tracking Control 57 Internet-Draft LDAP Session Tracking Control May 2007 67 version 3 (LDAP) clients can include session tracking identifiers 68 with their LDAP requests. This information is provided through 69 controls in the requests the clients send to LDAP servers. The LDAP 71 identifiers in the log messages it writes, enabling LDAP requests in 72 the LDAP server's logs to be correlated with activity in logs of 74 session tracking information to be generated by LDAP servers and 113 Internet-Draft LDAP Session Tracking Control May 2007 131 deployments, a majority of LDAP clients were desktop applications, [all …]
|
H A D | draft-zeilenga-ldap-noop-xx.txt | 13 The LDAP No-Op Control 22 discussion of this document will take place on the IETF LDAP 58 Zeilenga LDAP No-Op Control [Page 1] 65 This document defines the Lightweight Directory Access Protocol (LDAP) 81 This document defines the Lightweight Directory Access Protocol (LDAP) 89 For example, when the No-Op control is present in a LDAP modify 114 Zeilenga LDAP No-Op Control [Page 2] 121 The No-Op control is an LDAP Control [RFC4511] whose controlType is 126 The control is appropriate for request messages of LDAP Add, Delete, 132 When the control is attached to an LDAP request, the server does all [all …]
|
/netbsd-src/external/bsd/openldap/dist/doc/guide/admin/ |
H A D | intro.sdf | 9 {{TERM:LDAP}} Daemon, {{slapd}}(8). It is intended for new and 14 learning about {{TERM:LDAP}}, {{TERM:X.500}}, and directory services. 64 H2: What is LDAP? 66 {{TERM:LDAP}} stands for {{TERM[expand]LDAP}}. As the name suggests, 68 specifically {{TERM:X.500}}-based directory services. LDAP runs 70 services. LDAP is an {{ORG:IETF}} Standard Track protocol and is 71 specified in "Lightweight Directory Access Protocol (LDAP) Technical 74 This section gives an overview of LDAP from a user's perspective. 77 LDAP information model is based on {{entries}}. An entry is a 89 {{How is the information arranged?}} In LDAP, directory entries [all …]
|
/netbsd-src/external/bsd/openldap/dist/clients/tools/ |
H A D | common.h | 121 LDAP *tool_conn_setup LDAP_P(( int dont, void (*private_setup)( LDAP * ) )); 122 void tool_bind LDAP_P(( LDAP * )); 123 void tool_unbind LDAP_P(( LDAP * )); 125 void tool_exit LDAP_P(( LDAP *ld, int status )) LDAP_GCCATTR((noreturn)); 126 void tool_server_controls LDAP_P(( LDAP *, LDAPControl *, int )); 127 int tool_check_abandon LDAP_P(( LDAP *ld, int msgid )); 135 void tool_print_ctrls LDAP_P(( LDAP *ld, LDAPControl **ctrls ));
|
/netbsd-src/external/ibm-public/postfix/dist/proto/ |
H A D | ldap_table | 5 # Postfix LDAP client configuration 15 # Alternatively, lookup tables can be specified as LDAP databases. 17 # In order to use LDAP lookups, define an LDAP source as a lookup 32 # For details about LDAP SSL and STARTTLS, see the section 37 # When using LDAP to store lists such as $mynetworks, 50 # an arbitrary value. With LDAP databases it is not uncommon to 66 # GENERAL LDAP PARAMETERS 74 # The name of the host running the LDAP server, e.g. 80 # Depending on the LDAP client library you're using, it should 90 # With OpenLDAP, a (list of) LDAP URLs can be used to specify both [all …]
|