Chat now with support
Chat with Support

Identity Manager 8.2.1 - LDAP Connector for IBM AS/400 Reference Guide

Property mapping rules

  • CanonicalName ← vrtEntryCanonicalName

    vrtEntryCanonicalName is a virtual property, set to the canonical name of the object in the connector.

    Sample value:


  • cn ←→ os400-profile

    On the AS/400 system, os400-profile is the user ID.

    Sample value:


  • DistinguishedName ← vrtEntryDN

    vrtEntryDN is a virtual property, set to the DN of the object in the connector. Once this mapping rule has been created, edit the mapping rule by clicking on it. Then select Force mapping against direction of synchronization.

    Sample value:


  • ObjectClass ←→ objectClass

    The objectClass attribute (multi-valued) on the AS/400 system. Enable Ignore case sensitivity.

    Sample value:


  • StructuralObjectClass ← vrtStructuralObjectClass

    vrtStructuralObjectClass on the AS/400 system defines the single object class for the object type.

    Sample value:


  • UID_LDPDomain ← vrtIdentDomain

    Create a fixed value property variable on the AS/400 side called vrtIdentDomain that is set to the value $IdentDomain$. Map this to UID_LDPDomain. This will cause a conflict, and the Property Mapping Rule Conflict Wizard opens automatically.

    To resolve the conflict

    1. In the Property Mapping Rule Conflict Wizard, select the first option and click OK.

    2. On the Select an element page, select Ident_Domain and click OK.

    3. Confirm the security prompt with OK.

    4. On the Edit property page:

      1. Clear Save unresolvable keys.

      2. Select Handle failure to resolve as error.

    5. To close the Property Mapping Rule Conflict Wizard, click OK.

    Sample value:


  • vrtParentDN → vrtEntryParentDN

    Create a fixed-value property variable on the One Identity Manager side called vrtParentDN equal to a fixed string with value $UserLocation$. Map this to vrtEntryParentDN on the AS/400 side.

    Sample value:


  • vrtRDN → vrtEntryRDN

    Create a new variable on the One Identity Manager side of type Format Defined Property with the name vrtRDN. Set its value to os400-profile=%CN%. Then map this to vrtEntryRDN on the AS/400 side.

    Sample value:


  • userPassword → os400-password

    Used to change a user’s AS/400 password. A condition needs to be set on this rule to map the password only when there is a value to be copied.

    To add a condition

    1. Create the mapping.

    2. Edit the property mapping rule.

    3. Expand the Condition for execution section at the bottom of the dialog.

    4. Click Add condition and set the following condition (a blank password is indicated by using two apostrophe characters).


  • UID_LDAPContainer ← vrtEmpty

    This is a workaround needed to support group mappings. Create a new fixed-value variable on the AS/400 side of type String with no value called vrtEmpty. Map this to UID_LDAPContainer. This generates a property mapping rule conflict.

    To resolve the conflict

    • In the Property Mapping Rule Conflict Wizard, highlight Select this option if you do not want to change anything and click OK.

Related topics

Object matching rules

  • DistinguishedName (primary rule) vrtEntryDN

    vrtEntryDN is a virtual property, set to the DN of the object in the connector. This forms a unique ID to distinguish individual user objects on the AS/400 system.

    To convert this mapping into an object matching rule

    1. Select the property mapping rule in the rule window.

    2. Click in the rule view toolbar.

      A message appears.

    3. Click Yes to convert the property mapping rule into an object matching rule and save a copy of the property mapping rule.

    4. Open the new object matching rule in the top window and clear the Case sensitive check box.

    Sample value:


Related topics

Sample user mapping

The following figure shows the user mapping in operation.

Group mapping information

This section shows a possible mapping between a group profile in AS/400 and the standard One Identity Manager database table called LDAPGroup. User and group information on the AS/400 is stored in the same container, so a filter needs to be set up to tell these apart.

  • When creating the group mapping, add a new schema class as follows.

    Table 4: Schema class settings



    Schema type


    Display name


    Class name


    Select objects: Condition


    Select objects: Ignore case


  • Map the LDAPGroup (all) schema class to this new schema class, group_os400_usrprf, for this group mapping.

For more detailed information about setting up mappings, see the One Identity Manager Target System Synchronization Reference Guide.

Detailed information about this topic
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating