Cisco Unity Connection Provisioning Interface (CUPI) API -- For End Users -- System Configuration

From DocWiki

Revision as of 23:05, 13 December 2010 by Gscorbin (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Links to Other API pages: Cisco_Unity_Connection_APIs

CUPI for End Users Guide Contents
API Overview
Basics, Voice Name, Greetings
Unified Messaging Accounts
Alternate Devices
Directory
Enabling and Disabling Greetings
Location
Private Lists
SMTP Proxy Addresses
System Configuration
Transfer Options

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>

Rating: 0.0/5 (0 votes cast)

Personal tools