ldap objectclass
AKBK Home :: LDAP
:: ObjectClasses ::
Object Class: top
ID: 2.5.6.0
BNC Syntax: 2.5.6.0 NAME 'top'
MUST ( objectClass )
rfc2256
Extended by objectClass: alias,
applicationEntity,
applicationProcess,
bootableDevice,
certificationAuthority,
country,
cRLDistributionPoint,
dcObject,
device,
dmd,
domain,
extensibleObject,
groupOfNames,
groupOfUniqueNames,
ieee802Device,
ipHost,
ipNetwork,
ipProtocol,
ipService,
locality,
nisMap,
nisNetgroup,
nisObject,
oncRpc,
organization,
organizationalRole,
organizationalUnit,
person,
posixAccount,
posixGroup,
shadowAccount,
strongAuthenticationUser,
uidObject,
userSecurityInformation,
Attributes:
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: 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:
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:
|
