A Forum reader recently asked:
“I’m trying to create a pushback rule on password changes on a eDir2eDir driver with a distribution password. I have pushback rules working on regular attributes, but I can’t get it to work here. Is this possible to do?”
And here’s the response from Jeff Johnson …
Here is a rule I have on the publisher-matching of an eDir2eDir driver. If a certain criteria is met on this match, the password is pushed back. This may help you.
<rule> <description>If match found on ADD force Vault password back to NOS if Staff or Faculty</description> <conditions> <or> <if-op-attr mode="nocase" name="StudentADD" op="equal">true</if-op-attr> </or> <or> <if-op-attr mode="nocase" name="eduPersonAffiliation" op="equal">staff</if-op-attr> <if-op-attr mode="nocase" name="eduPersonAffiliation" op="equal">faculty</if-op-attr> </or> </conditions> <actions> <do-set-src-password> <arg-string> <token-dest-attr class-name="User" name="nspmDistributionPassword"/> </arg-string> </do-set-src-password> <do-break/> </actions> </rule>
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.