Jump to: navigation, search

Hypertext Transfer Protocol

Also known as HTTP. The protocol that is used most commonly in the World Wide Web to transfer information from web servers to web browsers.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Transport Layer Security

Also known as TLS. An industry-standard protocol for secure communications on the Internet. It is the successor of Secure Sockets Layer (SSL) 3.0.
Genesys supports the use of the TLS protocol to secure data exchange between Genesys components.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Hypertext Transfer Protocol Over Secure Socket Layer

Also known as HTTPS. A secure version of the Hypertext Transfer Protocol, it is the combination of a normal HTTP interaction over an encrypted Secure Sockets Layer (SSL) or Transport Layer Security (TLS) connection.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Security

Genesys Web Engagement supports HTTPS/SSL/TLS to protect data over the web.

  • All connections can be secured, including connections from the browser to the Web Engagement server.
  • Applications defined in Configuration Server can have both HTTP and HTTPS connections.

Transport Layer Security (TLS) is supported above Java containers, Jetty and Apache Tomcat. The user data submitted from the browser tier is always sent through secure connections.

Important
Genesys performs security testing with OWASP Zed Attack Proxy (ZAProxy) to protect the Genesys Web Engagement solution against known vulnerabilities. For details, see Security Testing with ZAProxy.

Genesys Web Engagement includes additional security configurations that can be used with your GWE installation:

Next Steps

After you configure security for Genesys Web Engagement, you can configure features to enable additional functionality.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on September 6, 2016, at 23:57.