OK, I have worked around the limitation of the GroupWise driver that it
cannot do a graft. The way the process will work is that the client will
migrate all the users into a "Migrated" container while the GroupWise
driver is down. We will graft them all there, then bring up the driver.
This works, I have tested it, and the user can then log in via LDAP
using their eDir password.

Problem is that the client wants to now move the user to a real
context, I put in a policy to handle this:

<rule>
<description>[WATTS] Synth LDAP DN</description>
<conditions>
<or>
<if-operation mode="case" op="equal">add</if-operation>
<if-operation mode="case" op="equal">modify</if-operation>
<if-operation mode="case" op="equal">move</if-operation>
<if-operation mode="case" op="equal">rename</if-operation>
</or>
</conditions>
<actions>
<do-set-dest-attr-value name="59028">
<arg-value>
<token-parse-dn dest-dn-format="ldap">
<token-xpath expression="@qualified-src-dn"/>
</token-parse-dn>
</arg-value>
</do-set-dest-attr-value>
</actions>
</rule>

And this does appear to work, as you see the updated LDAP context in
the GroupWise-->Account tab of the user object in ConsoleOne. However,
after doing this, logging in with the GroupWise client returns the
dialog "LDAP failure detected".


--
rrawson
------------------------------------------------------------------------
rrawson's Profile: http://forums.novell.com/member.php?userid=4898
View this thread: http://forums.novell.com/showthread.php?t=369695