...
Participants and absents
ChairBerg, Anna-Lis <anna-lis.berg@difi.no>
Klaus Vilstrup Pedersen
Lefteris Leontaridis
Attendees
Aksamit, Mikael <mikael@aksamit.se>Johannes Hunderi
Helger, Philip <philip.helger@brz.gv.at>
Langøy, Bård <bard.langoy@pagero.com>
Fabio Vigna
Jacob Lund Mogensen
Erlend Klakegg Bergheim
Even Østvold
Edmund Gray
Siarhei BaidunJens Aabol
Fabio Vigna
Luca Chiecchio
Agenda
Topics not discussed
...
- TB AP sends a transaction to a system under test (SUT)
- Prerequisites:
- SUT URL and AP certificate must be user provided
- SUT must be automatically registered in a (new) TB SMP with special ID, using the Proxy AP URL and the SUT AP certificate
- DNS timing must be considered
- Proxy AP must find the correct URL from the Orchestration layer based on SBDH Instance ID; it must than proxy the binary stream "as is" to SUT AP URL
- Input params:
- SBDH - XML binary serialized (xs:base64binary)
- Document Type ID
- Process ID
- Sending Participant Identifier
- Receiver Participant Identifier (SUT participant ID)
- Transmission Instance ID (Orchestration layer provided)
- Payload
- SBDH - XML binary serialized (xs:base64binary)
- Return values:
- None
- Prerequisites:
- TB AP send return value for transmission back to Orchestration Layer (asynchronous response to the above call)
- Input Params:
- Original MDN as byte[]
- REM or some other generic XML format
- Return values:
- None
- Input Params:
- TB AP receives a transaction from a SUT AP.
- Prerequisite:
- Every TB AP must be registered in an SMP with its own ID, using the Proxy AP URL and the TB AP certificate
- Each TB AP gets its own certificate
- Each test transmission targets exactly one TB AP (and not all in parallel)
- Each SUT AP must perform an SMP client lookup with the TB AP participant ID
- Received AS2 message (byte[]) including the AS2 headers - should be recorded by Proxy AP (to Orchestration layer)
- Input params:
- SBDH values for matching with the recorded values (see prerequisites)
- Document Type ID (must be predefined by OpenPEPPOL)
- Process ID (must be predefined by OpenPEPPOL)
- Sending Participant Identifier (SUT participant ID)
- Receiver Participant Identifier (TB AP participant ID)
- Transmission Instance ID
- SBDH values for matching with the recorded values (see prerequisites)
- Things to be communicated to Orchestration layer
- Transmission Instance ID as proof that message was received by TB AP
- Return values to sending SUT AP:
- MDN
- MDN is proxied by the Proxy AP which records the contents to the Orchestration Layer
- MDN
- Verification of MDN received by TB AP:
- Manually only atm
- Prerequisite:
AS4
- Basically identical to AS2
- Problem: payload encryption
- SUT sends to TB AP
- Encrypted with Proxy AP Cert
- Send to Proxy AP
- Proxy AP decrypts Message, sends to Orchestration Layer, re-encrypts and sends to TB AP
- TB AP creates Receipt
- Encrypted with Proxy AP Cert
- Send to Proxy AP
- Proxy AP decrypts Receipt, sends to Orchestration Layer, re-encrypts and sends to SUT AP
- TB AP sends to SUT
- see above
- SUT sends to TB AP
*Distinguish the software as “Testbed controller”
...