/mcpPUT /vmrest/configurationvalues/System.SA.UserInactivityTimeout HTTP/1.1 204 No Content Cache-Control: private Expires: Thu, 01 Jan 1970 05:30:00 IST Set-Cookie: JSESSIONIDSSO=2F68733BA443959388E841535A717DCC; Path=/; Secure; HttpOnly Set-Cookie: JSESSIONID=A982BB1A93DAB2C294A64BD5D7DD03D0; Path=/vmrest/; Secure; HttpOnly Set-Cookie: REQUEST_TOKEN_KEY=138477933938641394; Path=/; Secure; HttpOnly X-Frame-Options: SAMEORIGIN Content-Type: application/xml Date: Thu, 10 Dec 2015 06:55:12 GMT Server: XML <ConfigurationValue> <Value>36</Value> </ConfigurationValue> An example of PUT for TUI/VUI Logon Session Limit: PUT /vmrest/configurationvalues/System.Conversations.UserMaxConcurrentSessionsTUI XML <ConfigurationValue> <Value>3</Value> </ConfigurationValue> Cisco Unity Connection Provisioning Interface (CUPI) API -- Authentication Rules About Authentication Rules This section contains information on how to create, list, modify, and delete Authentication Rules. In Cisco Unity Connection, authentication rules govern user passwords, PINs, and account lockouts for all user accounts. You use authentication rules to secure how users access Connection by phone, and how users access Cisco Unity Connection Administration and the Cisco Personal Communications Assistant (PCA). For example, an authentication rule determines: • The number of failed sign-in attempts that are allowed before an account is locked • The number of minutes an account remains locked before it is reset • Whether a locked account must be unlocked manually by an administrator • The minimum length allowed for passwords and PINs • The number of days before a password or PIN expires Listing Authentication Rules Example 1 Cisco Unity Connection Provisioning Interface (CUPI) API 661 Cisco Unity Connection Provisioning Interface (CUPI) API for System Settings Cisco Unity Connection Provisioning Interface (CUPI) API -- Authentication Rules