From Bright Pattern Documentation
Jump to: navigation, search
 
Line 3: Line 3:
  
 
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).
 
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')
  
  

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 >