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 offering manager 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
Canonicalize incoming xml message from TCH before validating the signature on TCH Connector component.
Hello IBM Partners,
This is in regards to pmr TS005056798
At Huntington, we are using FTM 3.2.3 Ifix4 for TCH integration.
As you might already know TCH Bank test upgraded from RTP 2.9 version to 2.10 version on the evening of 02/16/2021. Starting the morning of 02/17/2021, Huntington is not able to sign on to the TCH Bank test; and all of the SNM(System Notification Messages) that we are receiving are rejected by FTM through 690 error code indicating a failure on the digital signature validation of the XML payload.
Upon further analysis and a couple of calls with TCH’s Development team, we understood below:
1. TCH started using a new platform for the MQ integration
2. The new platform essentially has the same functionality as the old but is built to support the new 2.10 specifications
3. The new platform has introduced blank spaces in between the XML elements of the XML payloads unlike the older system which used to remove all/any blank spaces before sending to the FIs
Due to #3, we are seeing that Huntington through FTM is failing to parse the XML message since FTM does not canonicalize the payload before validating the digital signature. Due to this the messags are failed at TCH connector while validating the signature
Do not place IBM confidential, company confidential, or personal information into any field.