Previous Topic: Propagate Global User Changes

Next Topic: Example: Modify Complex Attribute and Propagate Changes to Accounts

Example: Modify a Global User and Propagate Changes to Associated Accounts

<?xml version="1.0" encoding="UTF-8"?>
<modifyRequest xmlns="urn:oasis:names:tc:SPML:1:0" xmlns:dsml="urn:oasis:names:tc:DSML:2:0:core">
    <operationalAttributes></operationalAttributes>
    <identifier type="urn:oasis:names:tc:SPML:1:0#DN">
        <id>User=_spml_user,Domain=EXAMPLE_DOMAIN,Server=Server</id>
    </identifier>
    <modifications>
        <modification name="comments" operation="replace">
            <dsml:value>new comment</dsml:value>
        </modification>
        <modification name="syncAccounts" operation="replace">
            <dsml:value>true</dsml:value>
        </modification>
    </modifications>
</modifyRequest>

But because the SPML Manager doesn't display "syncAccounts" attribute in the "Modify" tab for any object apart from the Global User. So, to propagate changes made to Global Users' complex attributes like "address", the user will have to manually add the operational attribute "syncAccounts" to the modification request. This is done by pressing the "Show Hidden Attributes" button then select "New Operational Attribute". Once the new field is added, specify the name of the field to be "syncAccounts" and set it to true.