|
From RFC 2251 (complete section quoted below) "Attributes
MUST have at least one value when stored".
To releat
Charles' question, why do you need to store an empty attribute? Empty
attributes are meaningless: LDAP does not have any concept of null values.
You can empty an attribute after instantiating it, if you want
to.
"4.1.8. Attribute
An attribute consists of a type and one or more values of that type. (Though attributes MUST have at least one value when stored, due to access control restrictions the set may be empty when transferred in protocol. This is described in section 4.5.2, concerning the PartialAttributeList type.) Attribute ::= SEQUENCE { type AttributeDescription, vals SET OF AttributeValue } Each attribute value is distinct in the set (no duplicates). The order of attribute values within the vals set is undefined and implementation-dependent, and MUST NOT be relied upon."
|
Title: RE: [ActiveDir] Windows 2000 Professional Client (Native/Mixed mode)
- [ActiveDir] Empty values in attributes Ryjouk, Valeri (Valeri)
- RE: [ActiveDir] Empty values in attributes Charles Oppermann
- RE: [ActiveDir] Empty values in attributes Ryjouk, Valeri (Valeri)
- RE: [ActiveDir] Empty values in attributes Charles Oppermann
- RE: [ActiveDir] Empty values in attributes Ryjouk, Valeri (Valeri)
- RE: [ActiveDir] Empty values in attribute... Steve Judd
- RE: [ActiveDir] Empty values in attributes Ryjouk, Valeri (Valeri)
- RE: [ActiveDir] Empty values in attribute... Steve Judd
