(Created page with "<translate>= Security and Authentication= Either HTTP or HTTPS transport can be configured. The same setting applies to the entire Configuration Web Portal server. For product...") |
|||
| Line 1: | Line 1: | ||
<translate>= Security and Authentication= | <translate>= Security and Authentication= | ||
| − | + | HTTP digest access authentication is used to authenticate the access attempts. The provided username is checked against the list of users configured at the contact center (tenant) level. Moreover, the session is established provided that the supplied credentials are authenticated and that the user’s role indicates the user's authorization to perform operations. | |
| − | + | Standard HTTP response codes whose meaning conforms to the original specification (RFC 2616) are not discussed in this guide. For specification of such responses, see section 10 of http://www.ietf.org/rfc/rfc2616.txt. This document only specifies the response codes whose description deviates from the original specification (e.g., is defined more narrowly or has a different meaning). | |
Revision as of 23:48, 6 December 2018
Contents
- Introduction
- API Specification
Security and Authentication
HTTP digest access authentication is used to authenticate the access attempts. The provided username is checked against the list of users configured at the contact center (tenant) level. Moreover, the session is established provided that the supplied credentials are authenticated and that the user’s role indicates the user's authorization to perform operations.
Standard HTTP response codes whose meaning conforms to the original specification (RFC 2616) are not discussed in this guide. For specification of such responses, see section 10 of http://www.ietf.org/rfc/rfc2616.txt. This document only specifies the response codes whose description deviates from the original specification (e.g., is defined more narrowly or has a different meaning).