Share via


LDAPControl

A version of this page is also available for

Windows Embedded CE 6.0 R3

4/8/2010

This structure is used to represent both client-side and server controls.

Syntax

typedef struct ldapcontrol {
  PWCHAR ldctl_oid;
  struct berval ldctl_value;
  BOOLEAN ldctl_iscritical;
} LDAPControl, *PLDAPControl;

Members

  • ldctl_oid
    Control type, represented as a string, such as 1.2.840.113556.1.4.805.
  • ldctl_value
    Data associated with the control, if any.
  • ldctl_iscritical
    Indicates whether the control is critical, called the Criticality field.

Remarks

Beginning with LDAP 3, you can extend LDAP operations through the use of controls. Server controls can be sent to the server or returned to the client with any LDAP message. Client controls extend the behavior of the LDAP API on the client side only and are never sent to the server. All supported controls are stored as object identifiers (OIDs) in the Directory Service root.

The ldctl_iscriticalmember allows an extended operation to succeed when the server or client does not support the control. If the value of this field is zero, the server and/or client ignores the control if it is not supported and carries out the operation. If the value is nonzero, the operation is carried out only if the control is recognized by the server and/or client.

Requirements

Header winldap.h
Windows Embedded CE Windows CE .NET 4.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

Reference

LDAPMessage