|Attention: DocWiki has reached EOL and will be decommissioned January 25, 2019.|
Cisco Unity Connection Provisioning Interface (CUPI) API -- Authentication and Authorization
Links to Other API pages: Cisco_Unity_Connection_APIs
|CUPI Guide Contents|
|API Overview |
Index of All CUPI Documentation
About CUPI Authentication and Authorization
CUPI uses the same authentication and authorization scheme that the administration console uses. This means that the objects an administrator has access to when authenticated are determined by the roles to which the administrator is assigned.
CUPI authenticates by using standard HTTPS and Basic authentication, so that credentials can be passed by using typical mechanisms to send username and password via HTTP headers.
Authentication Rules API
In Cisco Unity Connection, the authentication rules govern user passwords, PINs, and account lockouts for all user accounts. You use the authentication rules to secure how users access Unity Connection by phone, and how users access Cisco Unity Connection Administration and the Cisco Personal Communications Assistant (Cisco 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. Administrator can use this API to create/update/delete/fetch the authentication rules. You can update various attributes of authentication rule using this API.