This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
As a Java client program I want to use SSL session resumption on different ports.
Some FTPS servers can force the client to use session resumption. For example FileZilla server shown in screenshot. In this case the client must take the SSL session of the command channel and reuse it in the data channel on a different port! Java on IBM i only supports session resumption on the same port.
The Oracle Java version has the same problem, but it exists a workaround. Basically you can overwrite the port in session cache with the current data port so it will be reused. Because the IBM Java version is obfuscated (and different), this workaround is not possible.
I see two possible solutions. The first one would be a switch, so I can bind the session to address only. The second one would allow a workaround similar to the workaround on Oracle Java.
We have a FTPS client and our customer wants to transfer data to a FileZilla server. The server forces SSL session resumption.
Our FTPS client is implemented in Java. Currently we use a QSHELL call to run a CURL command. I mention this because we had to use a CURL version with OpenSSL. The CURL version from yum does not work either.
Do not place IBM confidential, company confidential, or personal information into any field.