Expand description

Contains al the basic LDAP types

Structs

a wrapped error in case parsing fails to get proper error output the chumsky errors themselves lack Display and std::error::Error implementations
a distinguished name is a unique identifier for an entry within the LDAP tree, it is comprised of a comma-separated ordered list of RelativeDistinguishedName components
a key string is a string limited to the characters that are safe to use in a key context, e.g. a relative distinguished name, without encoding
represents an object in the LDAP tree we would use ldap3::SearchEntry but then we would not be able to derive Diff easily
in some locations LDAP allows OIDs with an optional length specifier to describe attribute types with a length limit
a relative distinguished name is one of the components of a distinguished name usually a single pair of a keystring or an OID along with its attribute value but it can also be a plus sign separated string of several such pairs
represents the object to request from an LDAP server to figure out which features,… it supports

Enums

LDAP allows the use of either a keystring or an OID in many locations, e.g. in DNs or in the schema
an operation to perform to turn one LDAP object into another. we purposefully only include operations here that operate without moving the object to a different DN

Functions

parses an RDN with attribute values being represented either as a string or an array of integers
hash function for ObjectIdentifier based on string representation since ObjectIdentifier does not implement Hash
parses a series of hex-encoded bytes (always even number of hex digits)
parses a KeyString in locations where it is single-quoted
parses a hex-encoded binary attribute value in an RDN
parses a plain string attribute value in an RDN
parses either a binary or a plain attribute value in an RDN
serialize RDN attribute values as string if possible falling back to array of numbers of necessary