Skip to Main Content
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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on May 11, 2023

Configure AT-TLS-Usage in Mainframe Agents

We would like to set per zos-agent if AT-TLS should be used for encryption or not. Also, the default port of the protocol configured in the URL should be used automatically.

Our zOS systems are configured to use AT-TLS for external repository Nexus.

We tried using https://<nexus> in to store component versions to nexus. This leads to the problem that IBM JRE (buztool) AND AT-TLS encrypt the traffic. Since nexus decrypts only once, the traffic remains encrypted once.

There is a workaround: configure with http://<nexus>:443. But this URL cannot be used in "normal" systems and irritates normal users

The advantage of this idea is that different AT-TLS configurations of uploading and downloading agents would be possible, because the Nexus URL at the uploaded component version would work for all agents. In addition, the confusing workaround URL could be avoided.

Idea priority Medium