AUTACK Secure authentication and acknowledgement

Syntax Development Group (SDG)

AUTACK is a message authenticating sent, or providing secure acknowledgement of received interchanges, groups, messages or packages.

A secure authentication and acknowledgement message can be used to:

a) give secure authentication, integrity or non-repudiation of origin to messages, packages, groups or interchanges.

b) give secure acknowledgement or non-repudiation of receipt to secured messages, packages, groups or interchanges.

Header

Position
Segment
Name
Max use
  1. To head, identify and specify a message.

    1. Data element S009/0057 is retained for upward compatibility. The use of
    S016 and/or S017 is encouraged in preference.
    2. The combination of the values carried in data elements 0062 and S009 shall
    be used to identify uniquely the message within its group (if used) or if
    not used, within its interchange, for the purpose of acknowledgement.
  2. Segment group 1
    Repeat 99
    1. To specify a security mechanism applied to a EDIFACT structure (i.e.: either message/package, group or interchange).

    2. To identify a security algorithm, the technical usage made of it, and to contain the technical parameters required.

    3. Segment group 2
      Repeat 2
      1. To convey the public key and the credentials of its owner.

      2. To identify a security algorithm, the technical usage made of it, and to contain the technical parameters required.

      3. To contain the result of the security mechanisms.

        1. S508, two occurrences shall be used in the case of signature algorithms
        requiring two parameters to express the result.
        In the case of an RSA signature, only one occurrence of S508 shall be
        used.
        In the case of a DSA signature two occurrences of S508 shall be used.
  3. To contain details related to the AUTACK.

  4. Segment group 3
    Repeat 9999
    1. To refer to the secured EDIFACT structure and its associated date and time.

      1. D5(050, 040) If first, then all
      2. D1(070, 090) One and only one
      3. D5(060, 040) If first, then all
      4. D5(080, 070) If first, then all
    2. To identify the applicable header, and to contain the security result and/or to indicate the possible cause of security rejection for the referred value.

  5. Segment group 4
    Repeat 99
    1. To establish a link between security header and security trailer segment groups.

      1. 0534, the value shall be identical to the value in 0534 in the
      corresponding USH segment.
    2. To contain the result of the security mechanisms.

      1. S508, two occurrences shall be used in the case of signature algorithms
      requiring two parameters to express the result.
      In the case of an RSA signature, only one occurrence of S508 shall be
      used.
      In the case of a DSA signature two occurrences of S508 shall be used.
  6. To end and check the completeness of a message.

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.