Cisco Unity Connection Provisioning Interface (CUPI) API -- For End Users -- System Configuration
From DocWiki
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
| - | + | {| border="1" class="wikitable" | |
| - | {| | + | |
| - | + | ||
|- | |- | ||
| - | + | ! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Cisco_Unity_Connection_Provisioning_Interface_(CUPI)_API_--_For_End_Users|CUPI for End Users Overview ]] | |
|} | |} | ||
Latest revision as of 18:02, 15 April 2012
| Back to: CUPI for End Users Overview |
|---|
Contents |
About System Configuration
There is no symmetry between the administrator CUPI URI's for configuration values and the end user access to configuration values. Anything that an end user needs to have read access to has its own URI that an end user can get to. End users cannot get to configuration values directly; for example, they cannot use the /vmrest/configurationvalue URI. If they attempt to use it, they will get access denied.
A client using an end user's credentials may need to know some information about the system. Currently that information involves two configuration values that an administrator can set:
System.Messaging.CumiAccessSecureMessageAttachments System.Messaging.CumiAllowSecureMessageHeaders
Both settings need to be exposed to end users, but end users cannot access configuration values directly. To resolve this issue, we created a way to expose some system values an end user client may need to see using the following URI:
GET http://<server>/vmrest/systemconfiguration
This URI can be accessed by any authenticated user, including an end user. It returns a SystemConfiguration object that currently has two fields:
<SystemConfiguration> <SecureMessageHeaders>false</SecureMessageHeaders> <SecureMessageAttachmentDownload>false</SecureMessageAttachmentDownload> </SystemConfiguration>