This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 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
Specific links you will want to bookmark for future use
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.