This is an IBM Automation portal for Cloud Management 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 updateson 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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
conman to authenticate users through WAS/WLP and retrieve LDAP group to user information and authorize using group in assigni
DWC and composer are able to authenticate LDAP users and authorize using LDAP groups and assign security roles accordingly, but conman doesn't authenticate using LDAP hence can't authorize using LDAP groups and assign security roles. Separate ACLs (stanza in security file) have to be specified with user IDs in order for CLI users to be authorized and respective roles assigned. This defeats the purpose of having LDAP groups and requires the security roles to be maintained in multiple places. A work around is to use OS level groups, but it still requires two entries, one for DWC/composer using the LDAP group and the other for CLI users using the OS group.
DWC and composer authenticate using the integration with LDAP configured in WAS/WLP, but conman doesn't. This RFE is for conman to adopt the same authentication and authorization mechanism as DWC/composer.
Please refer to Case No. TS004486686 for more details.
Do not place IBM confidential, company confidential, or personal information into any field.