Choosing secure communication protocols
- Last Updated: October 1, 2019
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
To guard against the inherent security problems associated with network traffic, and to provide a greater level of security for your applications, you can encrypt an application's configuration file and application-component downloads by using a secure communication protocol.
For example, you can use HTTPS to encrypt network traffic with a combination of symmetric and asymmetric ciphers. For more information on symmetric and asymmetric ciphers, see the Digitally signing files.
Secure protocols that you can use, depending on the server type (Web server, file server, or application server) where the files are hosted, include:
- HTTPS (requires the use of an adapter)
- Application server S (codebase downloads only)
- Application server DCS (codebase downloads only)
For more information on communication protocols for application configuration file and codebase downloads, see Host your WebClient Deployment.