EANCOM® 2002 S4 Part II
KEYMAN Security key and certificate manangement message
6. Examples 
 

The following examples will show how the message type KEYMAN can be used in order to transmit either a public key or a certificate reference.

Example 1

In the following example the public key of the sender identified with the GLN 4012345262698 is sent to a business partner in order to enable him to verify digital signatures in future transmissions.

UNH+KEY0001+KEYMAN:4:1:UN:EAN001'    Message header of the service message KEYMAN
USL+1+ZZZ:ABC-LIST' The list of valid keys is identified as ABC-LIST.
USC++3:PUBLIC KEY 01' The transmitted public key is identified as PUBLIC KEY 01.
USA+6:16:1:10:1:7:1+13:010001*12:CF8516555.........7E7406D7'                The algorithm used for generating digital signatures is RSA, the padding mechanism is specified in ISO 9796 # 2. The modulus of the public key is 010001. The public key of the sender is CF8516555.........7E7406D7.
UNT+5+KEY0001' Message trailer, the total number of segments equals 5.

Example 2

In the following example a reference to a certificate issued by a trust centre identified with the GLN 5412345000006 is sent to a business partner in order to enable him to verify digital signatures in future transmissions.

UNH+KEY0001+KEYMAN:4:1:UN:EAN001'                                                          Message header of the service message KEYMAN
USL+1+ZZZ:ABC-LIST' The list of valid certificates is identified as ABC-LIST.
USC+AXZ4711+4::5412345000006:2+3' The reference of the certificate issued by the trust centre identified with the GLN 5412345000006 is AXZ4711. The syntax of the certificate is X.509.
USA+6:16:1:10:1:7:1' The algorithm used for generating digital signatures is RSA, the padding mechanism is specified in ISO 9796 # 2.
UNT+5+KEY0001' Message trailer, the total number of segments equals 5.

Note:
The EDI interchange will include the UNB..UNZ segments and, if applicable, the UNG..UNE segments. (See part 1 section 5.7).

© Copyright GS1 Edition 2016