IBM Support

Signature Verification Problem with WebSphere Partner Gateway 6.0 RNIF

Troubleshooting


Problem

WebSphere Partner Gateway (WPG) 6.0 signature verification error

Resolving The Problem


In case of certain signature verification failures due to altered service content or digital signature foot-print, WPG 6.0 does not fail the inbound RNIF documents and passes them onto the backend application. All WPG 6.0 customers (on any FixPack levels) using RNIF transactions should download and apply the iFix as below.

iFix for Signature verification problem on WPG 6.0 FP7

This solution is for the Signature verification issue - APAR JR31231. This fix corrects the behavior of WPG 6.0 inbound RNIF document processing in case of certain signature verification failures. Earlier even when the signature verification would fail for certain scenarios, the document was processed successfully. After applying this fix, such documents would be marked as failed.

Important Note:

  1. Implication from applying JR31231 fix: This fix would rectify signature verification failure issues, but at same time, customers might see transactions with certain partners failing in case CRLF canonicalization has been performed on the WPG 6.0 inbound RNIF document.
  2. WPG 6.0 FP7 is a pre-requisite for this iFix. It is recommended to migrate to WPG 6.0 FP7 before applying this iFix.
  3. If there are any other fixes already applied involving common.jar file on WPG 6.0 FP7 level, then this iFix would need a special build. Please contact IBM support for special build requests.

Please follow the below instructions to apply this fix.

1. Download the common.jar file from 6.0.0.7-WPG-Advanced-Enterprise-JR31231
2. Stop the Router server.
3. Take a back up of the existing common.jar at <WPG Hub>/router/lib/
4. Replace the downloaded jar in the above location.
5. Start the Router server.

Impact Analysis tool

The impact analysis tool identifies the partners which may have potential signature verification failures. This tool is available for download below:

ImpactAnalysis_12Dec08.shImpactAnalysis_12Dec08.batdb2_indexes_12Dec08.sqloracle_indexes_12Dec08.sql

Follow the appropriate instructions for DB2 and Oracle as stated below to execute the Impact Analysis Tool.

Steps to execute Impact Analysis tool on DB2:

A. Download the tool.
Download the appropriate ImpactAnalysis_12Dec08.bat or ImpactAnalysis_12Dec08.sh file as per the platform and save it in a <localpath>.

B. Preparation for running the tool.
  1. Take the database backup.
  2. On the DB2 command prompt connect to database and execute attached db2_indexes_12Dec08.sql file.
    • This can be done by using db2 –td! –f <localpath/db2_indexes_12Dec08.sql>
  3. Make sure to execute the DB2 RunStats command for bp_rnstatedtl table.

C. Executing the tool.
  1. On the DB2 command prompt execute the downloaded <localpath>/ImpactAnalysis_12Dec08.bat OR <localpath>/ImpactAnalysis_12Dec08.sh file providing appropriate input parameters, such as Database Type (DB2), Database Name, User, Password, From Date, To Date. For example <localpath>/ImpactAnalysis_12Dec08.bat DB2 bcgapps bcgdb Pass#123 2008-01-20 2008-01-31
  2. The results of this tool will be available in the <localpath>/ImpactQueryResults.txt file.
  3. This results file will list affected partner’s Business ID, and the documents from these partners need further analysis for determination of the cause of signature verification failure.

Steps to execute Impact Analysis tool on Oracle:

A. Download the tool.
Download appropriate ImpactAnalysis_12Dec08.bat or ImpactAnalysis_12Dec08.sh file as per the platform and save it in a <localpath>.

B. Preparation for running the tool.
  1. Take the database backup.
  2. Create required indexes by connecting to database as schema user, and then executing attached oracle_indexes_12Dec08.sql.
  3. Ensure that schema statistics are up to date.

C. Executing the tool.
  1. Ensure that ORACLE_HOME environment variable is set pointing to the proper oracle installation location.
  2. Execute the downloaded <localpath>/ImpactAnalysis_12Dec08.bat OR <localpath>/ImpactAnalysis_12Dec08.sh file providing appropriate input parameters, such as Database Type (ORACLE), SID, Schema User, Schema Password, From Date, To Date. For example <localpath>/ImpactAnalysis_12Dec08.bat ORACLE orcl bcgdb Pass#123 2008-01-20 2008-01-31
  3. The results of this tool will be available in the <localpath>/ImpactQueryResults.txt file.
  4. This results file will list the affected partner’s Business ID, and the documents from these partners need further analysis for determination of the cause of signature verification failure.

[{"Product":{"code":"SSDKKW","label":"WebSphere Partner Gateway Advanced Edition"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"6.0;6.0.0.1;6.0.0.2;6.0.0.3;6.0.0.4;6.0.0.5;6.0.0.6;6.0.0.7","Edition":"Advanced;All Editions","Line of Business":{"code":"LOB02","label":"AI Applications"}},{"Product":{"code":"SSDKJ8","label":"WebSphere Partner Gateway Enterprise Edition"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":" ","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"6.0.0;6.0.0.1;6.0.0.2;6.0.0.3;6.0.0.4;6.0.0.5;6.0.0.6;6.0.0.7","Edition":"Enterprise","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21330341