Document History

1. Overview

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

2.    Description

Adjustment MDLP Connector code to Support MDLP manual signature approach via SAP GUI and Crypto Pro SSF integration.

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 if token is expired until token renewal by 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 case Java part use HTTPs the binding shall be created for new Web services

New transaction /K3T/RU_SSF_C Russia MDLP Certificate assignment created to maintain certificate assignment.

New field “Signature required” added to transaction /K3T/RU_CONF node Configuration ID.

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 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

The following corrections implemented into transaction /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 not be send to MDLP system by program (only using approval button via transaction /K3T/RU_MONITOR)

The following corrections implemented into program /K3T/RU_MDLP_IN (Inbound message processing):

• 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 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 separate interfaces created to execute report sending including manual signature function module /K3T/RU_MDLP_REQ_SIGNED / proxy class /K3T/CO_RU_MDLP_REQ_SIGNED

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

• /K3T/CO_RU_GET_OMS_AUTH

• /K3T/CO_RU_MDLP_CHECK_TOKEN

• /K3T/CO_RU_MDLP_REQ_SIGNED

• /K3T/CO_RU_MDLP_UPDATE_TOKEN

• /K3T/CO_RU_UPDATE_OMS_TOKEN

New RFC interfaces created at Java (called from ABAP part using RFC function modules):

• /K3T/RU_GET_OMS_AUTH - Get Auth string for signature for OMS token (manual signature)

• /K3T/RU_MDLP_CHECK_TOKEN - Russia MDLP Get token for Config ID

• /K3T/RU_MDLP_REQ_SIGNED - Russia MDLP send message (manual signature)

• /K3T/RU_MDLP_UPDATE_TOKEN - Russia MDLP Update token for Config ID

• /K3T/RU_UPDATE_OMS_TOKEN - Get new token from OMS (manual signature)

3.    Solution

Import related to the transport request.

3.1    Correction instruction ATTP 3.0

3.2    Correction instruction ATTP 3.1

3.3    Correction instruction ATTP 3.2

4.    Recommendation

TO BE ADDED

5.    Source code objects