A Forum reader recently asked:
"I have IDM 3.5 with a Identity Vault and other drivers, such as AD, JDBC, and Notes. Can I modify a custom attribute on users in a OU in my IDV? This operation is captured by a loopback driver that create a user on another OU of my driver, with some attributes populated."
And here's the response from Father Ramon ...
Here's what you need to do:
1. Use the null driver rather than the loopback driver.
2. Add a User to the subscriber filter.
3. Set it to synchronize on the subscriber channel and ignore on the publisher channel.
4. Add the Description attribute to the User class in the filter
5. Set it to notify on the subscriber channel and ignore on the publisher channel.
6. Add a subscriber channel event transformation - something like this:
<description>create portal user</description>
<if-class-name mode="nocase" op="equal">User</if-class-name>
<if-op-attr mode="nocase" name="Description"
<do-set-local-variable name="portalDN" scope="policy">
<do-add-src-attr-value class-name="User" name="Surname">
<description>Veto further processing</description>
7. Duplicate the last action in the first rule for each attribute you want to copy from the original object to the new object.
For information on the difference between a loopback driver and a null driver, see:
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.