This portal is to open public enhancement requests against IBM Z Software 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Thanks for the quick reply and clarity. This can be closed.
Assess AT-TLS support with development team
The use of (unsecured) HTTP to access EKMF Web is a configurable option.
It is IBM's recommendation to configure EKMF Web to disable HTTP and only use HTTPS and use trusted CA-signed certificates to secure the connection.
With native support for HTTPS in EKMF Web there is no need to use AT-TLS.
The mTLS support is intended for use with the EKMF API and the client certificate replaces RACF credentials as the means of authentication.
This removes the need to store (username and password) credentials with the calling application.
If mTLS is used to log on to EKMF Web as a key administrators using a browser, EKMF Web performs authentication in the same way. RACF authenticaton isn't bypassed, it just relies on a certificate rather than RACF (username and password) credentials.