PingDirectory

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

UUID

1.3.6.1.1.16.1

128-bit (16 octets) Universally Unique Identifier (UUID) used for Uniform Resource Names as defined in RFC 4122

For example, a4028c1a-f36e-11da-ba1a-04112154bd1e

Attribute Type Description

1.3.6.1.4.1.1466.115.121.1.3

Syntax for the AttributeTypeDescription rule based on RFC 4517

Binary

1.3.6.1.4.1.1466.115.121.1.5

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

Bit String

1.3.6.1.4.1.1466.115.121.1.6

Sequence of binary digits based on RFC 4517

For example, '0010111’B

Boolean

1.3.6.1.4.1.1466.115.121.1.7

TRUE or FALSE

Certificate

1.3.6.1.4.1.1466.115.121.1.8

BER/DER-encoded octet strings based on an X.509 public key certificate as defined in RFC 4523

Certificate List

1.3.6.1.4.1.1466.115.121.1.9

BER/DER-encoded octet string based on an X.509 certificate revocation list as defined in RFC 4523

Certificate Pair

1.3.6.1.4.1.1466.115.121.1.10

BER/DER-encoded octet string based on an X.509 public key certificate pair as defined in RFC 4523

Country String

1.3.6.1.4.1.1466.115.121.1.11

Two character country code specified in ISO 3166

For example, US, CA, and so forth

The current implementation for Country String:

  • Only verifies that values are two printable characters, where the set of printable characters is defined in RFC 2252.

  • Does not check that the value is a valid ISO 3166 country code.

DN

1.3.6.1.4.1.1466.115.121.1.12

Distinguished name of an entry as defined in RFC 4514

Delivery Method

1.3.6.1.4.1.1466.115.121.1.14

Sequence of services in preference order by which an entity receives messages as defined in RFC 4517

For example, videotext $ telephone

Directory String

1.3.6.1.4.1.1466.115.121.1.15

String of one or more characters from the Universal Character Set (UCS) using UCS Transformation Format 8 (UTF-8) encoding of the string

DIT Content Rule Description

1.3.6.1.4.1.1466.115.121.1.16

DITContentRuleDescription as defined in RFC 4517

DIT Structure Rule Description

1.3.6.1.4.1.1466.115.121.1.17

DITStructureRuleDesciption as defined in RFC 4517

Enhanced Guide

1.3.6.1.4.1.1466.115.121.1.21

Combination of attribute types and filter operators to be used to construct search filters as defined in RFC 4517

For example, person#(sn$EQ)#oneLevel

Facsimile Telephone Number

1.3.6.1.4.1.1466.115.121.1.22

Fax telephone number on the public switched telephone network as defined in RFC 4517

Fax

1.3.6.1.4.1.1466.115.121.1.23

Image generated using Group 3 fax process as defined in RFC 4517

Generalized Time

1.3.6.1.4.1.1466.115.121.1.24

String representing data and time as defined in RFC 4517 YYYYMMDDHHMMSS[.|,fraction][(+|-HHMM)|Z]

For example, 201103061032, 201103061032-0500, or 201103061032Z(Z indicates Coordinated Universal Time)

Guide

1.3.6.1.4.1.1466.115.121.1.25

Attribute types and filter operators as defined in RFC 4517

IA5 String

1.3.6.1.4.1.1466.115.121.1.26

String of zero or more characters from the International Alphabet 5 (IA5) character set as defined in RFC 4517

Integer

1.3.6.1.4.1.1466.115.121.1.27

String representations of integer values

For example, the character string 1234 represents the number 1234 as defined in RFC 4517

JPEG

1.3.6.1.4.1.1466.115.121.1.28

Image in JPEG File Interchange Format (JFIF) as defined in RFC 4517

Matching Rule Description

1.3.6.1.4.1.1466.115.121.1.30

MatchingRuleDescription as defined in RFC 4512

Matching Rule Use Description

1.3.6.1.4.1.1466.115.121.1.31

Attribute types to which a matching rule is applied in an extensibleMatch search filter

Name and Optional UID

1.3.6.1.4.1.1466.115.121.1.34

Distinguished name and an optional unique identifier that differentiates identical distinguished names (DNs) as defined in RFC 4517

For example, uid=jsmith,ou=Peo- ple,dc=example,dc=com#'0111’B

Name Form Description

1.3.6.1.4.1.1466.115.121.1.35

NameFormDescription as defined in RFC 4512

Numeric String

1.3.6.1.4.1.1466.115.121.1.36

Sequence of one or more numerals and spaces as defined in RFC 4517

For example, 14 848 929 102

Object Class Description

1.3.6.1.4.1.1466.115.121.1.37

ObjectClassDescription as defined in RFC 4512

OID

1.3.6.1.4.1.1466.115.121.1.38

Object identifier as defined in RFC 4512

Other Mailbox

1.3.6.1.4.1.1466.115.121.1.39

Specifies an electronic mailbox as defined in RFC 4517

For example, otherMailbox = google $ user@gmail.com

Octet String

1.3.6.1.4.1.1466.115.121.1.40

Sequence of zero or more octets (8-bit bytes) as defined in RFC 4517

Postal Address

1.3.6.1.4.1.1466.115.121.1.41

Strings of characters that form a multi-line address in a physical mail system. Each component is separated by a $

For example, 1234 Main St.$Austin, TX 78744$USA

Protocol Information

1.3.6.1.4.1.1466.115.121.1.42

Undefined

Presentation Address

1.3.6.1.4.1.1466.115.121.1.43

String encoded OSI presentation address as defined inhttps://tools.ietf.org/html/rfc1278[RFC 1278]

For example, TELEX+00728722+RFC-1006+03+10.0.0.6

Printable String

1.3.6.1.4.1.1466.115.121.1.44

String of one or more printable ASCII alphabetic, numeric, and punctuation characters as defined in RFC 4517

RFC3672 Subtree Specification

1.3.6.1.4.1.1466.115.121.1.45

Syntax based on subtree specification as defined as RFC 3672

Supported Algorithm

1.3.6.1.4.1.1466.115.121.1.49

Octet string based on the LDAP-encoding for a supported algorithm value that results from the BER encoding of a SupportedAlgorithm ASN.1 value

Telephone Number

1.3.6.1.4.1.1466.115.121.1.50

String of printable international telephone number representations in E.123 format as defined in RFC 4517

For example, +1 512 904 5525

Teletex Terminal Identifier

1.3.6.1.4.1.1466.115.121.1.51

Identifier and telex terminal as defined in RFC 4517

Telex Number

1.3.6.1.4.1.1466.115.121.1.52

String representing the telex number, country code, and answerback code as defined in RFC 4517

For example, 812374, ch, ehhg

UTC Time

1.3.6.1.4.1.1466.115.121.1.53

Character string representing the data and time in UTC Time format as defined as RFC 4517: YYMMDDHHMM[SS][(+|-HHMM)|Z], where Z is the coordinated universal time.

For example, 0903051035Z, 0903051035-0500

LDAP Syntax Description

1.3.6.1.4.1.1466.115.121.1.54

SyntaxDescription as defined inhttps://tools.ietf.org/html/rfc4512[RFC 4512]

Substring Assertion

1.3.6.1.4.1.1466.115.121.1.58

Syntax for assertion values in an extensible match as defined in RFC 4517

Authentication Password Syntax

1.3.6.1.4.1.4203.1.1.2

Encoded password storage syntax as defined in RFC 3112

For example, the syntax specifies the storage scheme in brackets: <storage-scheme>$<auth component>$<auth value>

For example, SSHA$xdEZWRqgyJk=$egDEFDXvdeeEnXUEIDPnd39dkpe=

User Password Syntax

1.3.6.1.4.1.30221.1.3.1

Encoded password storage syntax as defined in RFC 2307

For example, the syntax specifies the storage scheme in brackets: {SSHA}XaljOF0ii3fOwCrU1klgBpWFayqSYs+5W1pMnw==

Relative Subtree Specification

1.3.6.1.4.1.30221.1.3.2

Similar to the RFC 3672 subtree specification except it uses an LDAP search filter as the specification filter

Absolute Subtree Specification

1.3.6.1.4.1.30221.1.3.3

Syntax for a subset of entries in a subtree based on RFC 3672

Sun-defined Access Control Information

1.3.6.1.4.1.30221.1.3.4

Syntax for access control instructions used in Sun Directory Servers

Compact Timestamp

1.3.6.1.4.1.30221.2.3.1

Syntax based on Compact Timestamp ISO 8601 format

For example, 20110306T102532