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

ID: 2.5.6.1

According to the letter of the standard, an alias may point at any entry. It is beneficial for aliases to be 'schema consistent'.

The following two checks should be made:

  1. The Relative Distinguished Name of the alias should use an attribute type normally used for naming entries of the object class of the main entry.
  2. If the entry (aliased object) were placed where the alias is, there should be no schema violation.

BNC Syntax: 2.5.6.1 NAME 'alias' SUP top STRUCTURAL MUST aliasedObjectName

rfc1617

Extends objectClass:

Attributes:

Requires :


Comments

Your email address:
Add Your comments:

Attribute: aliasedObjectName

Description:
The aliasedObjectName attribute is used by the directory service if the entry containing this attribute is an alias.

BNC Syntax: 2.5.4.1 NAME 'aliasedObjectName' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE

rfc2256

Syntax: DN

ID : 1.3.6.1.4.1.1466.115.121.1.12

Values in the Distinguished Name syntax are encoded to have the representation defined in [5]. Note that this representation is not reversible to an ASN.1 encoding used in X.500 for Distinguished Names, as the CHOICE of any DirectoryString element in an RDN is no longer known.

Examples (from [5]):

  

CN=Steve Kille,O=Isode Limited,C=GB
OU=Sales+CN=J. Smith,O=Widget Inc.,C=US
CN=L. Eagle,O=Sue\, Grabbit and Runn,C=GB
CN=Before\0DAfter,O=Test,C=GB
1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB
SN=Lu\C4\8Di\C4\87

BNC Syntax: 1.3.6.1.4.1.1466.115.121.1.12 DESC 'DN'

rfc2252

Equality Matching: distinguishedNameMatch

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: 2.5.13.1 NAME 'distinguishedNameMatch' SYNTAX 1.3.6.1.4.1.1466.115.121.1.12

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