...

This document describes changes in the 3Keys MDLP connector ABAP part.

2.    Description

Adjustment MDLP Connector code to Support MDLP New functionality for Russia MDLP connector implemented to support manual signature approach via SAP GUI and Crypto Pro SSF integrationsoftware installed on the user local PC. Combined scenario with non-resident, resident MDLP cabinet with manual signature and without manual signature are supported.

In case of manual signature scenario token is stored at MDLP Connector Java part and updated from transaction /K3T/RU_MONITOR by user. MDLP system interaction works automatically if connector has active token and stopped wait if token is expired until token renewal renewed by the user.

Prerequisite of manual signature are the following:

• installed Crypto Pro SSF software

• installed certificate to Crypto Pro container

• correct signature customising on ATTP system (Crypto Pro library)

• correct signature customising on MDLP Connector settings (SSF id for configuration, manual approval, manual signature)

• in installed on the user local PC

• Crypto Pro setup refer to the configuration guide

• In case Java part use HTTPs the binding shall be created for new Web services

New transaction /K3T/RU_SSF_C Russia - “Russia MDLP Certificate assignment assignment” created to maintain certificate assignment to the user and configuration ID.

New field “Signature required” added to transaction /K3T/RU_CONF node Configuration ID to activate the manual signature for the Configuration ID. The field “User approval” shall be active to stop message in status ‘01’ and wait for the user Approval in the transaction /K3T/RU_MONITOR.

The following corrections implemented into transaction /K3T/RU_MONITOR:

• New menu “Manual Signature” with option “Update Token” added to the program toolbar. If token is still active update token option will be provided via confirmation Popup . To to update token

• Approval button logic corrected to send selected report using manual signature. Additional popup window appears to execute manual signature before sending report via SAP GUI and Crypto Pro SSF integration. After signature report is send to MDLP Connector Java part

• MDLP Message menu button processing corrected to check token before sending request to MDLP system

...

• , before sending the signed report to the connector java part.

• The check of the valid MDLP token added to the MDLP Message menu buttons like “Display message XML” “Display Response XML” etc.

The check of the valid MDLP token added to the following transactions:

• /K3T/RU_MDLP_SN_INFO Russia MLDP serial number info

...

• check for active token at MDLP Connector

The following corrections implemented into program /K3T/RU_MDLP_DISPATCHER:

...

• report manual signature filter - reports with manual signature configurations will be processed only in case active token exists for configuration

• API methods will be used to receive information for reports with manual signature from MDLP independently of system customizing (This correction works at inbound processing modules, for example, Function module /K3T/RU_AIF_IN_SCN will receive hierarchy information using API method not by using 210 / 220 XML message)

The following corrections implemented into transaction /K3T/RU_OMS_TOKEN - Russia OMS token:

• report manual signature filter - OMS token for manual signature configurations will not be updated by program if program is executed on background mode (only dialog mode)

• manual signature - If OMS token for manual signature configuration need to be updated additional popup window appears to execute manual signature to sign authorisation data via SAP GUI and Crypto Pro SSF integration. After signature data is send to MDLP Connector Java part and token is updated at ATTP system

...

New Web service interfaces created at Java (called from ABAP part using proxy classes):

...

3.    Solution

Import related to the transport request.

3.1    Correction instruction ATTP 3.0

...

4.    Recommendation

TO BE ADDEDFor customers without activation manual signature:

• Regression test for outbound and inbound messages (1031x, 6xxx)

Complete process testing for customers with active manual signature process.

5.    Source code objects