As many of you know, when creating new users in Dir via a template that
includes group memberships, the driver tries to add the unassociated user
to the group in the connected system before the driver has a chance to
give the user being added a DirXML association. This creates two problems
1.) The initial group member in Notes has the wrong naming format (i.e.
2.) The new user does not get correctly added to the group until the group
is modified again.
Based on a post in this forum (albeit related to the AD driver), a
suggestion was made to insert a rule to handle this. I tried it for the
Notes driver and it 'kinda' worked but not like I would've hoped. The TID
can be found here: http://wiki.novell.com/index.php/AD_Add_Groups_Policy
I've also pasted the rule below.
The result of this rule is as follows:
1.) The initial group modify in Notes still goes through, adding the
unassociated user to the group with the wrong naming format.
2.) The rule runs, but adds the user to the Notes Group as CN/Notes
Domain. It is taking the literal username out of the eDir group and
placing it in the Notes group and tagging a /Notes Domain on the end.
Is there a way to make this pretty and only add 1 user with the correct
syntax the first time?
<?xml version="1.0" encoding="UTF-8"?>
<description>Add new user to associated groups</description>
<token-src-attr name="Group Membership"/>
<token-xpath expression="query:readObject($srcQueryProcessor, '',
$current-node, 'Group','')/association/text()[. != '']"/>
<do-add-dest-attr-value class-name="Group" name="Member">