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 (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 Under review
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Oct 15, 2024

Extend "Role Mappings" in the "Map Users and Groups to Roles for Application" step of UCD to support more than 5 arguments.

WAS supports more arguments and UCD chops off anything after 5. This is causing issues in the deployment cycle and is a limitation to our processes.

 We are fully aware of how the configuration works in WAS Admin console and WAS Admin scripting, but that's not what we are looking for here as a solution.

 

The application EAR has a security constraint and an authentication role which needs the following mapping:

ESP#[-MapRolesToUsers [["AuthenticatedUser" "no" "no" "" "" "yes" "" ""]]]



The issue was never caught because it worked fine when the requirements were All Authenticated in Application Realm. When this was changed to

All Authenticated in Trusted Realm – that’s when the issue surfaced. We had a migration from Solaris to Linux, the former settings were in Solaris, and was later changed to Trusted realm in Linux.



 

Idea priority High
  • Admin
    Randy Langehennig
    Reply
    |
    Nov 7, 2024

    Thank you for submitting this idea. We are creating a discussion topic (Jira card) to review this with the plugin team. We will be in touch with you after we meet with additional updates.