ABL client default cipher suites for SSL

ABL client default ciphers list does not include all supported ciphers. Why some set of cipher suites has been picked vs another as defaults? Is this list going to be updated in the future release?

Supported ciphers for Progress OpenEdge clients:

• AES128-SHA256:
• AES256-SHA256:
• DHE-RSA-AES128-SHA256:
• AES128-GCM-SHA256:
• DHE-RSA-A ES128-GCM-SHA256:
• DHE-RSA-AES256-SHA256:
• ADH-AES128-SHA256:
• ADH-AES256-SHA256:
• ADH-AES128-GCM -SHA256:
• AES256-GCM-SHA384:
• DHE-RSA-AES256-GCM-SHA384:
• ADH-AES256-GCM-SHA384

The issue is with OE ABL client connecting to an external service.

The ABL client's default list of ciphers was incorrectly restricted by OE's use of the underlying TLS vendor. Why it was restricted is no longer the issue. What is important is that Progress has recognized the issue and is working to fix it so that customer's do not run into this issue again in the future. Once corrected, current expectation is that OE's default set of default ABL client ciphers will become inclusive of all the vendor's available ciphers. 

Implemented in OE 12.2 where the client now supports all ciphers supported by OpenSSL.

References to Other Documentation:
Progress Article(s):
ADH* series are not supported ciphers
Identifying what SSL/TLS ciphers a server supports.
How to set TLS/SSL protocols and ciphers to use in the HTTP client?
How to set Client SSL Protocols and Ciphers in OpenEdge
Identifying what SSL/TLS ciphers a server supports.
Ciphers supported by OpenEdge
Client stops reading through the available ciphers list 50% of the time when an unsupported cipher is encountered in the list