Apply modifications to attribute values
04changetype: modify identifies an existing entry. Within that record, add:, delete: and replace: introduce attribute modifications, each terminated by a line containing only a hyphen.
A final replace: description block followed immediately by a hyphen removes the attribute. This is an empty set, unlike description: which is a single empty string. A separate delete on an already absent attribute would fail. This is one illustrated successful request, not a real import.
Source for this drawing: RFC 2849 · Read RFC source: Change grammar and example 6 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
The hyphen terminates a modification block; a blank line separates records. Multiple modifications of one request act in their listed order, with LDAP atomicity rather than a guarantee across the whole file.
- The hyphen terminates a modification block; a blank line separates records. Multiple modifications of one request act in their listed order, with LDAP atomicity rather than a guarantee across the whole file.
- add: adds values; delete: removes listed values or the whole attribute when no values follow; replace: replaces all values and creates the attribute if necessary.
- replace: with no values removes an attribute if present and is harmless if absent. delete: of an absent attribute fails. A zero-length value is still one value. Actual LDAP matching, naming attributes, schema and authorization remain outside this simplified example.
Fictional directory data. Fragments illustrate the format; no file, URL or directory is accessed. Import outcomes still depend on schema, permissions and server support.
Read the RFC section ↗