Tim Kuehn (TDK Consulting Services Inc) asked a question.
Using forward proxies to solve the HTTP client TLS cert problem?
I've read that OE's client TLS cert management problem can be mitigated by using forward proxies. Has anyone done this and can share their experince?
Some KB links
https://community.progress.com/s/article/configuration-example-of-Apache-acting-as-a-forward-proxy-server-to-allow-the-use-of-ssl-sni-and-the-use-of-a-transparent-proxy-server
https://community.progress.com/s/article/the-abl-client-doesn-t-send-the-ssl-ciphers-and-protocol-when-establishing-a-secure-connection-to-a-remote-server-via-a-proxy
Support for client certificates was added for the ABL socket in 12.4. Are there other problems with support for mTLS that you know of?
They're not managed properly - instead of Progress managing certs automatically, Progress wants people to d/l certs using a browser and manually add them to the certstore.
That led to this IDEAS request:
https://openedge.ideas.aha.io/ideas/OPENEDGE-I-1106