5.7 Operation Data Caching

The mechanism that is available for required operation data caching required is the <operation-data> element. Because you might need to provision the SecretStore account from either an <add> or <modify-password> command, a logical place to implement the non-static data caching policy is in the Subscriber Command Transformation policy. The following example shows a typical SecretStore Provisioning element:

<operation-data> <nss-sync-data> <nss-target-user-dn> cn=GLCANYON,ou=finance,o=Testco Financials </nss-target-user-dn> <nss-app-username>GCANYON</nss-app-username> <password><!-- content suppressed --></password> <nss-passphrase-answer>50024222</nss-passphrase-answer> </nss-sync-data> </operation-data>

In the sample Finance department scenario from Figure 4-1, the following values are needed to populate the operation data payload: