DNS:

SSL

Provide additional FQDNs to the SSL Certificate that it will be validate.

IP:

SSL

Allows you to supply an IP address within the SAN list.  This is very unorthodox, as it is literally impossible to validate an IP, but sometimes required by an application or service as a way of providing the IP that the FQDN should resolve to as a security measure.

EMAIL:

SSL

Allows you to specify an email address in the SANs list.  This is usually only required for the certificate to be used to sign email communications and verify the owner of the certificate and domain.  Sometimes the application or service will send validation emails to the email address listed to ensure that the email is valid and can be responded to.

dn:
cn:
givenName:
telephoneNumber:
mail:
manager:
objectclass:
sn:

LDAP / LDIF

X.500 directory services were traditionally accessed via the X.500 Directory Access Protocol (DAP), which required the Open Systems Interconnection (OSI) protocol stack. LDAP was originally intended to be a lightweight alternative protocol for accessing X.500 directory services through the simpler (and now widespread) TCP/IP protocol stack.

dn: cn=John Doe,dc=example,dc=com
cn: John Doe
givenName: John
sn: Doe
telephoneNumber: +1 888 555 6789
telephoneNumber: +1 888 555 1232
mail: john@example.com
manager: cn=Barbara Doe,dc=example,dc=com
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: top

OID:
or simply the OID itself.

URI

An OID corresponds to a node in the "OID tree" or hierarchy, which is formally defined using the ITU's OID standard, X.660. The root of the tree contains the following three arcs:

• 0: ITU-T

• 1: ISO

• 2: joint-iso-itu-t

Each node in the tree is represented by a series of integers separated by periods, corresponding to the path from the root through the series of ancestor nodes, to the node. Thus, an OID denoting Intel Corporation appears as follows,

1.3.6.1.4.1.343

and corresponds to the following path through the OID tree:

• 1 ISO

• 1.3 identified-organization,

• 1.3.6 DoD,

• 1.3.6.1 internet,

• 1.3.6.1.4 private,

• 1.3.6.1.4.1 IANA enterprise numbers,

• 1.3.6.1.4.1.343 Intel Corporation

A textual representation of the OID paths is also commonly seen; for example,

• iso.identified-organization.dod.internet.private.enterprise.intel

Each node in the tree is controlled by an assigning authority, which may define child nodes under the node and delegate assigning authority for the child nodes. Continuing with the example, the node numbers under root node "1" are assigned by ISO; the nodes under "1.3.6" are assigned by the US Department of Defense; the nodes under "1.3.6.1.4.1" are assigned by IANA; the nodes under "1.3.6.1.4.1.343" are assigned by Intel Corporation, and so forth.