Default attribute syntaxes
PingDirectory server supports a large set of Attribute Syntax rules for applications.
The default Attribute Syntax rules available for the server are listed in the following table.
LDAP Syntax | OID | Description | ||
---|---|---|---|---|
|
|
128-bit (16 octets) Universally Unique Identifier (UUID) used for Uniform Resource Names as defined in RFC 4122 For example, |
||
|
|
Syntax for the |
||
|
|
Strings based on Basic Encoding Rules (BER) or Distinguished Encoding rules (DER) For example, an X.509 digital certificate or LDAP messages are BER encoded |
||
|
|
Sequence of binary digits based on RFC 4517 For example, |
||
|
|
|
||
|
|
BER/DER-encoded octet strings based on an X.509 public key certificate as defined in RFC 4523 |
||
|
|
BER/DER-encoded octet string based on an X.509 certificate revocation list as defined in RFC 4523 |
||
|
|
BER/DER-encoded octet string based on an X.509 public key certificate pair as defined in RFC 4523 |
||
|
|
Two character country code specified in ISO 3166 For example,
|
||
|
|
Distinguished name of an entry as defined in RFC 4514 |
||
|
|
Sequence of services in preference order by which an entity receives messages as defined in RFC 4517 For example, |
||
|
|
String of one or more characters from the Universal Character Set (UCS) using UCS Transformation Format 8 (UTF-8) encoding of the string |
||
|
|
|
||
|
|
|
||
|
|
Combination of attribute types and filter operators to be used to construct search filters as defined in RFC 4517 For example, |
||
|
|
Fax telephone number on the public switched telephone network as defined in RFC 4517 |
||
|
|
Image generated using Group 3 fax process as defined in RFC 4517 |
||
|
|
String representing data and time as defined in RFC 4517 For example, |
||
|
|
Attribute types and filter operators as defined in RFC 4517 |
||
|
|
String of zero or more characters from the International Alphabet 5 (IA5) character set as defined in RFC 4517 |
||
|
|
String representations of integer values For example, the character string |
||
|
|
Image in JPEG File Interchange Format (JFIF) as defined in RFC 4517 |
||
|
|
|
||
|
|
Attribute types to which a matching rule is applied in an |
||
|
|
Distinguished name and an optional unique identifier that differentiates identical distinguished names (DNs) as defined in RFC 4517 For example, |
||
|
|
|
||
|
|
Sequence of one or more numerals and spaces as defined in RFC 4517 For example, |
||
|
|
|
||
|
|
Object identifier as defined in RFC 4512 |
||
|
|
Specifies an electronic mailbox as defined in RFC 4517 For example, |
||
|
|
Sequence of zero or more octets (8-bit bytes) as defined in RFC 4517 |
||
|
|
Strings of characters that form a multi-line address in a physical mail system. Each component is separated by a For example, |
||
|
|
Undefined |
||
|
|
String encoded OSI presentation address as defined inhttps://tools.ietf.org/html/rfc1278[RFC 1278] For example, |
||
|
|
String of one or more printable ASCII alphabetic, numeric, and punctuation characters as defined in RFC 4517 |
||
|
|
Syntax based on subtree specification as defined as RFC 3672 |
||
|
|
Octet string based on the LDAP-encoding for a supported algorithm value that results from the BER encoding of a |
||
|
|
String of printable international telephone number representations in E.123 format as defined in RFC 4517 For example, |
||
|
|
Identifier and telex terminal as defined in RFC 4517 |
||
|
|
String representing the telex number, country code, and answerback code as defined in RFC 4517 For example, |
||
|
|
Character string representing the data and time in UTC Time format as defined as RFC 4517: For example, |
||
|
|
|
||
|
|
Syntax for assertion values in an extensible match as defined in RFC 4517 |
||
|
|
Encoded password storage syntax as defined in RFC 3112 For example, the syntax specifies the storage scheme in brackets: For example, |
||
|
|
Encoded password storage syntax as defined in RFC 2307 For example, the syntax specifies the storage scheme in brackets: |
||
|
|
Similar to the RFC 3672 subtree specification except it uses an LDAP search filter as the specification filter |
||
|
|
Syntax for a subset of entries in a subtree based on RFC 3672 |
||
|
|
Syntax for access control instructions used in Sun Directory Servers |
||
|
|
Syntax based on Compact Timestamp ISO 8601 format For example, |