Wrote a loop back driver to help with someone cleanup on unused
accounts. When trying to retrieve the values of DirXML-Associations into
a nodeset, I am unable to do so. Other attributes come back just fine.
The driver has admin rights and the end object has 3 valid driver
associations. Here's a code snippet:

<do-set-local-variable name="local.associations" scope="policy">
<arg-node-set>
<token-attr name="DirXML-Associations"/>
</arg-node-set>
</do-set-local-variable>

Here's the level 3 failing the return:

[06/15/11 10:35:17.416]:Cleanup Loopback ST: Action:
do-set-local-variable("local.associations",scope="policy",arg-node-set(token-src-attr("DirXML-Associations"))).
[06/15/11 10:35:17.417]:Cleanup Loopback ST:
arg-node-set(token-src-attr("DirXML-Associations"))
[06/15/11 10:35:17.417]:Cleanup Loopback ST:
token-src-attr("DirXML-Associations")
[06/15/11 10:35:17.418]:Cleanup Loopback ST: Query from
policy
[06/15/11 10:35:17.418]:Cleanup Loopback ST:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.0.4294">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query class-name="User"
dest-dn="\MMCF\MMCORG\RETIRED\USERS\BOENDD1" dest-entry-id="127466"
scope="entry">
<read-attr attr-name="DirXML-Associations"/>
</query>
</input>
</nds>
[06/15/11 10:35:17.420]:Cleanup Loopback ST: Pumping XDS to
eDirectory.
[06/15/11 10:35:17.421]:Cleanup Loopback ST: Performing
operation query for \MMCF\MMCORG\RETIRED\USERS\BOENDD1.
[06/15/11 10:35:17.423]:Cleanup Loopback ST: Query from
policy result
[06/15/11 10:35:17.423]:Cleanup Loopback ST:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.0.4294">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<output>
<instance class-name="User"
qualified-src-dn="O=MMCORG\OU=RETIRED\OU=USERS\CN=BOENDD1"
src-dn="\MMCF\MMCORG\RETIRED\USERS\BOENDD1" src-entry-id="127466"/>
<status level="success"></status>
</output>
</nds>
[06/15/11 10:35:17.425]:Cleanup Loopback ST: Token Value: {}.
[06/15/11 10:35:17.426]:Cleanup Loopback ST: Arg Value: {}.
[06/15/11 10:35:17.426]:Cleanup Loopback ST: Action:
do-for-each(arg-node-set(token-src-attr("DirXML-Associations"))).
[06/15/11 10:35:17.426]:Cleanup Loopback ST:
arg-node-set(token-src-attr("DirXML-Associations"))
[06/15/11 10:35:17.427]:Cleanup Loopback ST:
token-src-attr("DirXML-Associations")
[06/15/11 10:35:17.427]:Cleanup Loopback ST: Token Value: {}.
[06/15/11 10:35:17.428]:Cleanup Loopback ST: Arg Value: {}.
[06/15/11 10:35:17.428]:Cleanup Loopback ST:Policy returned:

I have also put the DirXML-Associations attribute into the filter to
see that the driver DOES infact, have rights to see that attibute. A
simple change to an attribute shows all 3 structured parts of that
attribute being read.

Help woud be much appreciated on this one!


--
plummb
------------------------------------------------------------------------
plummb's Profile: http://forums.novell.com/member.php?userid=15414
View this thread: http://forums.novell.com/showthread.php?t=440465