< Back to Top

AS2 Endpoint

This article describes AS2 Endpoint attributes and other information about AS2 as it relates to your trading partners.

AS2 Endpoint Attributes

The AS2 Endpoint has the following attributes:

Attribute Description
Partner URL  The URL pointing to the location where your trading partner receives messages. 
Partner AS2 Name The AS2 name your trading partner uses to send and receive messages from this Endpoint. 
My AS2 Name The AS2 name you use to send and receive messages from this Endpoint.
Inbound Section

The attributes in this section apply to messages being received by this endpoint.

Attribute Description
Verify Signed Payloads Select to ensure that when a signed payload is received, the signature is what you expect from your trading partner.  When you select this option:
  • The Require Signing check box displays. Select it to require that all messages be signed.
  • You are prompted to select the trading partner's signing certificate. See Selecting a certificate.
Accept Encrypted Payloads Select to accept encrypted inbound payloads. 
When you select this option:
  • The Require Encryption check box displays. Select it to require that all messages be encrypted.
  • You are prompted to select your decryption certificate. See Selecting a certificate.
Require HTTPS Select to require that Transport Layer Security (TLS) be used for inbound messages.
Outbound Section

The attributes in this section apply to messages being sent from this Endpoint.

Attribute Description
Subject Identifies the message and is returned in the human-readable section of an MDN if requested. 
Content Type Specify the format of the message being sent or allow the Cleo Integration Cloud to detect the content type automatically. This value is used when assembling and parsing messages. Choose from the following:
  • Auto Detect
  • EDIFACT
  • X12
  • XML
  • Binary
  • Plain Text
Note: Auto-detectable types include:
  • application/edifact
  • application/edi-x12
  • application/edi-tradacoms
  • application/xml (text/xml)
  • application/pdf
  • application/msword
  • application/x-msexcel
  • application/rtf
  • application/zip
  • image/bmp
  • image/gif
  • image/tiff
  • image/jpeg
  • text/plain
  • text/html
  • video/mpg
Sign Select this option to sign messages sent from this Endpoint. 
When you select Sign:
  • You are prompted to select your signing certificate. See Selecting a certificate.
  • Use the Signing Algorithm field (in the Advanced tab) to choose the algorithm you want to use to sign outbound messages.
Encrypt

Apply encryption to messages sent from this Endpoint. 

When you select Encrypt, you are prompted to select the trading partner's encryption certificate. See Working With Certificates.
Compress

Apply ZLIB compression to messages sent from this Endpoint. Choose this option for large files to conserve bandwidth and improve efficiency and security. 
Request MDN Receipts

Request MDN receipts when sending messages from this Endpoint. 

When you select this option, the following fields are displayed:

Type

Specify how you want MDN receipts generated. Choose from the following: 

  • Synchronous - MDN is generated as part of the same HTTP session. 
  • Asynchronous HTTP -- MDN is generated as part of a new HTTP session. 
  • Asynchronous HTTPS -- MDN is generated as part of a new HTTPS session. 
Require signing 

Select this option to require that all MDN receipts be signed. 

When you select this option, you are prompted to select the trading partner's signing certificate. This field is prefilled with the inbound signing certificate as the same certificate is commonly used for both. See Selecting a certificate.
Advanced Section Attributes in these sections extend configuration capabilities for this Endpoint with respect to Security and Connection & Transfer options.
Security Section
Attribute Description
Signing Algorithm

The algorithm you want to use to sign messages sent from this Endpoint. 

Choose from the following:

  • SHA-1
  • MD5 (cryptographically weak and should not be used unless no other Hash/MIC algorithm is available)
  • SHA-256 (default)
  • SHA-384
  • SHA-512
Encryption Algorithm

The algorithm you want to use to encrypt messages sent from this Endpoint. 

Choose from the following:

  • RC2/40
  • RC2/64
  • RC2/128
  • DES
  • TripleDES (default)
  • AES/128
  • AES/192
  • AES/256
  • RC4/40
  • RC4/64
  • RC4/128
TLS Protocol Version Minimum
Maximum
Select minimum and maximum versions for SSL/TLS protocol. Messages from systems using versions of SSL/TLS outside the range you specify are not accepted. 
Choose from the following:
  • SSL 3.0
  • TLS 1.0 (SSL 3.1)
  • TLS 1.1 (SSL 3.2)
  • TLS 1.2 (SSL 3.3)
  • No Maximum -- available only for the Maximum field.
TLS Minimum Encryption Key Size The minimum encryption key size allowed when selecting a TLS cipher. To prevent the use of low- or medium-strength ciphers, change from the default value of 0 to 112, 128, or 256 (depending on the requirement). Note that if this value is set too high, all ciphers are filtered out causing the No suitable cipher suites are enabled exception to occur.
TLS Ciphers

The cipher selected is used with the server for key exchange, encryption, and hashing. If the server does not support the cipher, a TLS handshake error will occur. 
Choose from the following: 

  • All - Present the list of supported ciphers to the server and allow the server to pick one. 
  • Select from list  - Display a list from which you choose a specific cipher.
TLS Renegotiation Allow TLS Legacy Renegotiation -- Allows legacy renegotiation. Otherwise, the extension described in RFC5746 will be used for renegotiation and any TLS clients must also support this extension. See RFC5746 for a description of the extension and the vulnerability it addresses. 
TLS Client Certificate If you want to use TLS client authentication, select the client certificate here. See Working With Certificates. 
HTTP Authentication If you want to use HTTP authentication, select Basic or Digest to display fields where you can enter Username, Password, and Realm.
Connection & Transfer Section
Attribute Description
Transfer Encoding

Chunked -- Message content is broken up into a number of chunks, each prefixed by its size in bytes.

Chunked encoding is useful when a large amount of data is being transferred and the total size of the response is not known until the request has been fully processed. 
Connection Timeout

The amount of time allowed for each read operation. 

Valid range is from 0 - n seconds

0 indicates no timeout. Default value is 150 seconds.
Outbound Transfer Retries

The number of retries permitted for failed outbound transfers, the time between retries, and whether to resume failed transfers. 

  • Maximum retry attempts -- Minimum value is 0 (no retries allowed) and maximum is 5.
  • Retry interval -- Enter a numeric value and either minutes or seconds to specify how much time should elapse between retries. 
  • Resume failed transfers -- Select this check box to retry failed transfers starting where they failed.

Connecting with Trading Partners over AS2

Partners connecting to CIC over AS2 should use the values displayed on the AS2 Endpoint screen.

mceclip0.png

The AS2 URL value is generated when Cleo configures your system for you.  It is possible for you to have multiple incoming URLs configured for partners who want to connect to CIC using AS2. Contact your system administrator for more information about your specific configuration.

The AS2-To Header and AS2-From Header come from the values you provide when you configure your endpoint.

Related articles