AKBKHOME Consulting Services Available : Linux, Embedded Linux, PHP and PHP-GTK, just Contact me at alan@akbkhome.com 
LDAP Schema | PHP Code doc | AKBK Home >>> Projects | Phpmole IDE | Diary | Photos  
search for in

Ldap Schema Viewer

Objectclass : certificationAuthority

ID: 2.5.6.16

No description available

BNC Syntax: 2.5.6.16 NAME 'certificationAuthority' SUP top AUXILIARY MUST ( authorityRevocationList $ certificateRevocationList $ cACertificate ) MAY crossCertificatePair

rfc2256

Extends objectClass:

Attributes:

Requires :
May Have:


Comments

Your email address:
Add Your comments:

Attribute: authorityRevocationList

Description:
This attribute is to be stored and requested in the binary form, as 'authorityRevocationList;binary'.

BNC Syntax: 2.5.4.38 NAME 'authorityRevocationList' SYNTAX 1.3.6.1.4.1.1466.115.121.1.9

rfc2256

Syntax: Certificate List

ID : 1.3.6.1.4.1.1466.115.121.1.9

Because of the incompatibility of the X.509(1988) and X.509(1993) definitions of revocation lists, values in this syntax MUST only be transferred using a binary encoding, by requesting or returning the attributes with descriptions "certificateRevocationList;binary" or "authorityRevocationList;binary". The BNF notation in RFC 1778 for "Authority Revocation List" is not recommended to be used.

BNC Syntax: 1.3.6.1.4.1.1466.115.121.1.9 DESC 'Certificate List'

rfc2252


Attribute: certificateRevocationList

Description:
This attribute is to be stored and requested in the binary form, as 'certificateRevocationList;binary'.

BNC Syntax: 2.5.4.39 NAME 'certificateRevocationList' SYNTAX 1.3.6.1.4.1.1466.115.121.1.9

rfc2256

Syntax: Certificate List

ID : 1.3.6.1.4.1.1466.115.121.1.9

Because of the incompatibility of the X.509(1988) and X.509(1993) definitions of revocation lists, values in this syntax MUST only be transferred using a binary encoding, by requesting or returning the attributes with descriptions "certificateRevocationList;binary" or "authorityRevocationList;binary". The BNF notation in RFC 1778 for "Authority Revocation List" is not recommended to be used.

BNC Syntax: 1.3.6.1.4.1.1466.115.121.1.9 DESC 'Certificate List'

rfc2252


Attribute: cACertificate

Description:
This attribute is to be stored and requested in the binary form, as 'cACertificate;binary'.

BNC Syntax: 2.5.4.37 NAME 'cACertificate' SYNTAX 1.3.6.1.4.1.1466.115.121.1.8

rfc2256

Syntax: Certificate

ID : 1.3.6.1.4.1.1466.115.121.1.8

Because of the changes from X.509(1988) and X.509(1993) and additional changes to the ASN.1 definition to support certificate extensions, no string representation is defined, and values in this syntax MUST only be transferred using the binary encoding, by requesting or returning the attributes with descriptions "userCertificate;binary" or "caCertificate;binary". The BNF notation in RFC 1778 for "User Certificate" is not recommended to be used.

BNC Syntax: 1.3.6.1.4.1.1466.115.121.1.8 DESC 'Certificate'

rfc2252


Attribute: crossCertificatePair

Description:
This attribute is to be stored and requested in the binary form, as 'crossCertificatePair;binary'.

BNC Syntax: 2.5.4.40 NAME 'crossCertificatePair' SYNTAX 1.3.6.1.4.1.1466.115.121.1.10

rfc2256

Syntax: Certificate Pair

ID : 1.3.6.1.4.1.1466.115.121.1.10

Because the Certificate is being carried in binary, values in this syntax MUST only be transferred using a binary encoding, by requesting or returning the attribute description "crossCertificatePair;binary". The BNF notation in RFC 1778 for "Certificate Pair" is not recommended to be used.

BNC Syntax: 1.3.6.1.4.1.1466.115.121.1.10 DESC 'Certificate Pair'

rfc2252


Attribute: objectClass

Description:
An LDAP server implementation SHOULD recognize the attribute types described in this section. The values of the objectClass attribute describe the kind of object which an entry represents. The objectClass attribute is present in every entry, with at least two values. One of the values is either "top" or "alias".

BNC Syntax: 2.5.4.0 NAME 'objectClass' EQUALITY objectIdentifierMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.38

rfc2256

Syntax: OID

ID : 1.3.6.1.4.1.1466.115.121.1.38

Values in the Object Identifier syntax are encoded according to the BNF in section 4.1 for "oid".

Example:


1.2.3.4
cn

BNC Syntax: 1.3.6.1.4.1.1466.115.121.1.38 DESC 'OID'

rfc2252

Equality Matching: objectIdentifierMatch

Description:

Servers SHOULD be capable of performing the following matching rules.

For all these rules, the assertion syntax is the same as the value syntax.

If the client supplies a filter using an objectIdentifierMatch whose matchValue oid is in the "descr" form, and the oid is not recognized by the server, then the filter is Undefined.

BNC Syntax: 2.5.13.0 NAME 'objectIdentifierMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.38

rfc2252


Contact me at alan@akbkhome.com - especially if you have some work for me :)