A Forum reader recently asked:

“I have created a mapping table with 3 columns (Location, Department and Context Code). I would like to create a placement rule that places the users in the correct eDirectory context, based on the Context code. The locations and department names in the table match the OUs in the tree. Does anyone know how to create a placement rule to use the mapping table?”

And here’s the response from David Gersic …


Here’s one I did. I used departmentNumber as the index in to the mapping table, and I put a default phone number attribute on the user as part of the create:

 <description>Add Department Phone Number</description>
   <if-class-name mode="nocase" op="equal">User</if-class-name>
  <do-add-dest-attr-value name="Telephone Number">
    <token-map dest="Default Phone Number" src="Department Number"
table="\[root]\niu\IDM\Policy and Data Library\Department Data Mapping
     <token-op-attr name="departmentNumber"/>
0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
By: dgersic
May 2, 2007
6:50 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow