Cloud Platform
This is an IBM Automation portal for Cloud Platform products. 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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM is positioning IBM Zert as security focal point on TLS and SSH sessions. The SMF 119 security data is provided by AT_TLS.
We think this is a good strategy to have this security information at a focal point in Zert. As such we try to deliver most TLS implementation with AT-TLS. We do see that the main reason not to use AT-TLS is that an application losses functionality because they are not AT-TLS controlled opr aware.
We would like to see that also Liberty and as such also z/OS Connect can use AT-TLS without loosing functionaliy.
So please add this functionality to Websphere / Liberty
We are strongly vote for this RFE, because we need ATTLSAWARE for in- and outbound communication in Liberty-Server.
When we now use AT-TLS on outbound communication, then all applications has to change their URLs from "https" to "http". If they have further SSL-aware parameters in their URL, they have to exclude it. Otherwise Liberty demands a SSL-configuration. What we need is an ATTLSAWARE-Parameter, that applications can use their https-URL, but Liberty checks, that TLS will be done by Comm-Server.
Now it is really confusing for applications. Use they "http" or "https". And furthermore it's a huge problem, moving applications from local Liberty to CICS-Liberty
Same procedure for incoming requests. We want to use the httpsPort in the endpoint-definition in server.xml. So, that it is clear, that we run with SSL.
Best regards,
Juergen (DATEV eG)