This is an IBM Automation portal for Integration 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.
See this idea on ideas.ibm.com
Based on this document,
https://www.ibm.com/docs/en/ibm-mq/9.4?topic=application-user-ids
If we use MQ Clients in Windows accessing an IBM MQ running on windows, we can have users ID up to 20 characters. But if the server is not windows, the limit is 12 character.
is there any particular reason for that? If IBM MQ is ready to have longer users, why not when a server is running on non-windows?
We want to move out from IBM MQ running on windows to IBM MQ on Containers using LDAP. We cant not authenticate in LDAP because IBM MQ Server (or i guess in this case the clients) are truncating the user name (sAMAccountName) to 12 characters.
We have several service accounts running around all environments that connect to IBM MQ (currently running on Windows, local users) with more than 12 characters, less than 20. Move to shorter names for all that services accounts (that they are running very importante applications) could cause us many problems.
It seems that clients (MQC, MQ Explorer) are configured to send sAMAccountName to IBM MQ to perform authentication. One solution could be to send another attribute to ibm mq for authentication.
BY example:
sAMAccountName: a-more-than-12-chars
ibmMQname: amt-12-chars
we can not move from IBM MQ Windows to IBM MQ Containers today.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.