Map Object Class Transformations This type of transformation allows mapping of objectclasses and attributes between a client application and the source directory. It also allows removing objectclasses and adding or removing attributes while writing to the directory or returning response to the client application.
This type of transformation allows general mapping that can make one objectClass, such as user, appear like another objectClass, such as inetOrgPerson. This ability is useful when an application is expecting a particular objectClass and attributes but the directory does not support that objectClass or attributes. It can perform several different types of manipulations based on the selected configuration parameters, such as attribute mapping, objectclass mapping, adding or removing attributes conditional on objectclass, filtering objectclasses during write operations or during modify operations. Map Object Class Transformation
The Map Object Class Transformation component inherits from the Transformation
A description of each property follows.
Basic Properties: | Advanced Properties: |
---|---|
↓ add-attribute | ↓ java-class |
↓ entry-match-filter | |
↓ entry-parent-suffix | |
↓ excluded-operation | |
↓ filter-attribute | |
↓ filter-objectclass-on-modify | |
↓ filter-objectclass-on-write | |
↓ map-attribute | |
↓ map-objectclass |
Description | Add an attribute to the entry during add operation. An optional objectclass name may be specified to add the attribute only for that objectclass. Add an attribute to the entry during add operation. An optional objectclass name may be specified to add the attribute only for that objectclass. In that case, the objectclass name must be prefixed to the attribute name, with ':' as the separator. For example, to add a userAccountControl attribute to only the user objectclass, use: user:userAccountControl=546. Similarly, to add displayName attribute with same value as cn attribute, use: displayName=%cn%. |
---|---|
Default Value | None |
Allowed Values | Source-attribute=value. |
Multi-valued | Yes |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Specifies the filter that the entry must match for this transformation to apply. |
---|---|
Default Value | None |
Allowed Values | A String |
Multi-valued | No |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Specifies an ascendant of the operation DN for this transformation to apply. |
---|---|
Default Value | None |
Allowed Values | A valid DN. |
Multi-valued | Yes |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Specifies operations on which this transformation never apply. This allows to restrict the regular behavior of this transformation. |
---|---|
Default Value | None |
Allowed Values | add - Specifies LDAP ADD operation. compare - Specifies LDAP COMPARE operation. delete - Specifies LDAP DELETE operation. extended - Specifies LDAP EXTENDED operation. modify - Specifies LDAP MODIFY operation. modifydn - Specifies LDAP MODIFYDN operation. search - Specifies LDAP SEARCH operation. |
Multi-valued | Yes |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Removes an attribute from the entry during add, modify operations and from all returned entries. A conditional objectclass name may be specified to remove the attribute only for that objectclass. Removes an attribute from the entry during add, modify operations and from all returned entries. A conditional objectclass name may be specified to remove the attribute only for that objectclass. In that case, the objectclass name must be prefixed to the attribute name, with ':' as the separator. For example, if you specify the value as 'samaccountname', it will remove samaccountname attribute from the entry during add and modify operations, and while returning the entry. Similarly if you specify the value as 'user:memberof', it will remove memberof attribute from the entry with user objetclass, during add and modify operations, and while returning the entry. |
---|---|
Default Value | None |
Allowed Values | A String |
Multi-valued | Yes |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Remove objectclasses during modify operations. Flag to determine whether or not to remove objectclasses during modify operations. Supported values include true (remove changes) and false (do not remove changes), where true is the default. |
---|---|
Default Value | true |
Allowed Values | true false |
Multi-valued | No |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Remove an objectclass during add and modify operations. Remove an objectclass during add and modify operations. An example is Microsoft Active Directory for Windows 2000 does not allow auxiliary object classes to be listed while adding an entry, while Microsoft Active Directory and ADAM for Windows Server 2003 does allow for auxiliary classes to be listed. For example, if the value is specified as 'person', person objectclass will be removed from the entry during add and modify operations. |
---|---|
Default Value | None |
Allowed Values | LDAP obejctclass syntax. |
Multi-valued | Yes |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Map a client attribute to a source attribute. Specifies the name of the attribute as seen by the client application and to be mapped to the attribute in the source directory. Example: displayName=%givenName% The client attribute displayName is mapped to givenName when sent to the source repository, and reverse mapped from givenName to displayName when read from the source repository and sent to the client application. |
---|---|
Default Value | None |
Allowed Values | Client-attribute=Source-attribute. |
Multi-valued | Yes |
Required | No |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Map a client objectclass to a source objectclass. Specifies the name of the objectclass as seen by the client application and to be mapped to the objectclass in the source directory. Example: inetOrgPerson=user The client objectclass inetOrgPerson is mapped to user when sent to the source repository, and reverse mapped from user to inetOrgPerson when read from the source repository and sent to the client application. |
---|---|
Default Value | None |
Allowed Values | Client-objectclass=Source-objectclass. |
Multi-valued | Yes |
Required | Yes |
Admin Action Required | None |
Advanced Property | No |
Read-only | No |
Description | Specifies the fully-qualified name of the Java class that provides the Map Object Class Transformation implementation. |
---|---|
Default Value | org.opends.server.core.transformations.attributetransformations.MapObjectClass |
Allowed Values | A java class that implements or extends the class(es) : org.opends.server.core.transformations.attributetransformations.TransformationAbstract |
Multi-valued | No |
Required | Yes |
Admin Action Required | None |
Advanced Property | Yes |
Read-only | No |