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 : dcObject

ID: 1.3.6.1.4.1.1466.344

An example entry would be:
dn: dc=critical-angle,dc=com
objectClass: top
objectClass: organization
objectClass: dcObject
dc: critical-angle
o: Critical Angle Inc.

BNC Syntax: 1.3.6.1.4.1.1466.344 NAME 'dcObject' SUP top AUXILIARY MUST dc

rfc2247

Extends objectClass:

Attributes:

Requires :


Comments

Your email address:
Add Your comments:

Attribute: dc

Description:
The DC (short for domainComponent) attribute type is defined as follows: The value of this attribute is a string holding one component of a domain name. The encoding of IA5String for use in LDAP is simply the characters of the string itself. The equality matching rule is case insensitive, as is today's DNS.

BNC Syntax: 0.9.2342.19200300.100.1.25 NAME 'dc' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE

rfc2247

Syntax: IA5 String

ID : 1.3.6.1.4.1.1466.115.121.1.26

The encoding of a value in this syntax is the string value itself.

BNC Syntax: 1.3.6.1.4.1.1466.115.121.1.26 DESC 'IA5 String'

rfc2252

Equality Matching: caseIgnoreIA5Match

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.

When performing the caseIgnoreMatch, caseIgnoreListMatch, telephoneNumberMatch, caseExactIA5Match and caseIgnoreIA5Match, multiple adjoining whitespace characters are treated the same as an individual space, and leading and trailing whitespace is ignored.

Clients MUST NOT assume that servers are capable of transliteration of Unicode values.

BNC Syntax: 1.3.6.1.4.1.1466.109.114.2 NAME 'caseIgnoreIA5Match' SYNTAX 1.3.6.1.4.1.1466.115.121.1.26

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 :)