Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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
  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 (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.

Status Delivered
Workspace Concert Workflows
Created by Guest
Created on Nov 5, 2025

Integration between Concert Workflows and Ansible Automation Platform

Is useful because actually Concert Workflows is integrated only with Ansible Tower (that use different API). Using the Ansible Tower authentication and building blocks in Concert are not working with Ansible Automation platiform (Looking at the Ansible integration blocks, I see that the "Ansible Tower" is available, but these blocks use the old API path, api/v2, instead of the correct one, api/controller/v2). This is the documentation of the new Ansible Automation Platform APIs: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/automation_execution_api_overview/index

The error raised when we try the authentication: 

message: "Ansible/Tower authentication failed with: 404 - "\n<!doctype html>\n<html lang=\"en\">\n<head>\n  <title>Not Found</title>\n</head>\n<body>\n  <h1>Not Found</h1><p>The requested resource was not found on this server.</p>\n</body>\n</html>\n""

Idea priority Urgent
  • Guest
    Nov 6, 2025

    I don't think the issue is with the authentication process, it's just basic authentication. The real problem lies in the URL endpoint In AAP, the path is /api/controller/v2, the CW blocks uses /api/v2

  • Guest
    Nov 5, 2025

    Since AAP has moved behind the eva hub, the authentication process has changed completely, as has the base URL for contacting the server......