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:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
DataStage MQ Connector does not use the user Id and password while setting up the connection
We tried to set up a connection from DataStage using MQ Connector to the MQ server that only works when there is no password authetication configured at the MQ end. The connection fails when MQ team enabled force password authentication while DataStage connects to MQ server.
With this current mode of communication, a valid MQ user authticated at the MQ end, is suffcient for DataStage to connect to MQ. But this set up is not acceptable for the MQ team, because without a need for password based authetication, anyone can connect to the MQ server if they come to know the authorized ID.
So this enhancement request is raised to enable -
MQ Connector to require user Id and password while setting up the connection to the MQ server.
Configuration at the MQ end that needs to be supported:
A PMR was raised with issue and following were the final comments-
Current implementation of the MQ Connector does not use the user Id and password while setting up the connection. The authentication and authorization is performed by MQ on the application level that does not require passing credentials. In order to support the MQ settings mentioned in the PMR description above, the connector must be modified. It should be treated as the enhancement of current functionality.
Engineering confirmed that this is design limitation and would require design changes to allow MQ Connector stage to support CHCKCLT(REQUIRED) and thus sending authentication structures to server.
Do not place IBM confidential, company confidential, or personal information into any field.