From Bright Pattern Documentation
Jump to: navigation, search
(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...")
 
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
<translate>= Security and Authentication=
 
<translate>= Security and Authentication=
Either HTTP or HTTPS transport can be configured. The same setting applies to the entire Configuration Web Portal server. For production deployments on public Internet only, HTTPS is enabled.
+
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.
  
The [https://tools.ietf.org/html/rfc6749#section-4.4 OAuth 2.0 Client Credentials Grant] (RFC 6749, Section 4.4) is used to authenticate clients of this API. The username is checked against the list of users configured for the provider and for having an appropriate role/privilege to add/delete/import tenants.
+
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).
  
 +
== Example ==
 +
Here is an example of how to authenticate in Python.
  
 +
auth=HTTPDigestAuth('Username', 'Password')
  
  
  
 
</translate>
 
</translate>

Latest revision as of 20:50, 30 July 2019

• 3.16 • 3.17 • 3.18

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).

Example

Here is an example of how to authenticate in Python.

auth=HTTPDigestAuth('Username', 'Password')


< Previous | Next >