/mcpPUT vmrest/users/<objectid>/credential/pin <?xml version="1.0" encoding="UTF-8"?> <Credential> <CantChange>true</CantChange> </Credential> Here is an example of changing a user's password such that the user cannot change it. PUT vmrest/users/<objectid>/credential/password <?xml version="1.0" encoding="UTF-8"?> <Credential> <CantChange>true</CantChange> </Credential> Note that the only difference in these examples is the URI; they both use the same Credentials object. Cisco Unity Connection Provisioning Interface (CUPI) API -- Changing Primary and Alternate Extensions About Changing Primary and Alternate Extensions A common scenario is having a primary extension that needs to be changed, but the old primary extension needs to be kept around as an alternate extension for that same user. This document describes the steps to make such a change. It shows how to either create a new alternate extension for a user, or update an existing alternate extension. Viewing the Primary Extension The user's primary extension is the DTMFAccessID field on the user object. The following is an example of a GET that lists the user object: GET /vmrest/users/<userobjectid> The user's primary extension will also show up in their list of alternate extensions with an IdIndex of 0. Updating the Primary Extension The following is an example of a PUT that modifies the DTMFAccessID of a user to 2001: PUT /vmrest/users/<userobjectid> <?xml version="1.0" encoding="UTF-8"?> <User> <DtmfAccessId>2001</DtmfAccessId> </User> The user's primary extension can also be updated through the user's alternate extensions URI by executing a PUT that modifies the alternate extension with an IdIndex of 0. Cisco Unity Connection Provisioning Interface (CUPI) API 193 Cisco Unity Connection Provisioning Interface (CUPI) API for User Account Settings Cisco Unity Connection Provisioning Interface (CUPI) API -- Changing Primary and Alternate Extensions