Same hash calculation from your original data file.ĪS1 clients can usually be configured to connect directly to You can verify his/her signature using the public key on your partner's SSL certificateĪnd that the cryptographic hash calculated from your partner's copy of your data file matches the

You will inspect your partner's MDN delivery receipt message, making sure that.

You will retrieve your partner's MDN delivery receipt message off your local email server using the POP3 protocol.

This step will be skipped if the MDN delivery receipt message was delivered directly to your email server in step #7. (The cleartext MDN delivery receipt message is rarely protected with SSL transport if relay servers are involved.)

If the MDN delivery receipt message were sent to your partner's local email server, it will now deliver it to your email server using the SMTP protocol.Īlong the way your partner's MDN delivery receipt message may traverse several intermediate email servers as it is relayed across the Internet or corporate email infrastructure.

(Credentials and the cleartext MDN delivery receipt message may be protected with SSL transport in this step.)

Often, this will be your partner's local email server. Your partner will send his/her MDN delivery receipt message to an email server via SMTP.(The signing step is optional and controlled by the original message sender.) Sign the hash (and some other information) with the private key on their SSL certificateĪnd create an MDN delivery receipt message. If you requested an MDN delivery receipt for your data file, your partner willĬalculate a cryptographic hash from the data file they received,.Identical to the data file you sent them. Your partner will also use the contents of the AS1 message to verify that the data file they now have is

If the message is signed, your partner will validate your signature using the public key on your SSL certificate.

If the message is encrypted, your partner will decrypt it using the private key on his/her SSL certificate.Your partner will retrieve your AS1 message off your partner's local email server using the POP3 protocol.This step will be skipped if the AS1 message was delivered directly to your partner's email server in step #2. (Cleartext message headers are rarely protected with SSL transport if relay servers are involved.) Along the way your AS1 message may traverse several intermediate email servers as it is relayed across the Internet or corporate email infrastructure. If the AS1 message was sent to your local email server, it will now deliver it to your partner's email server using the SMTP protocol.(Credentials and cleartext message headers may be protected with SSL transport in this step.) Often, this will be your local email server. You send the AS1 message to an email server via SMTP.(Both the encryption and signing steps are optional, but should be used when possible.) You encrypt a data file with the public key on your partner's SSL certificate and sign it with the private key of your organization's SSL certificate as you bundle everything into an AS1 message.(AS1 is the only ASx protocol that contains this requirement.) To trade SSL certificates and specific 'trading partner' names before any transfers can take place.ĪS1 trading partner names must really be email addresses. Like any other ASx file transfer, AS1 file transfers typically require both sides of the exchange It is probably the easiest ASx protocol to set up and work with, but it is It was the first ASx protocol developedĪnd established the signing, encryption and MDN conventions used in later AS2 and AS3 protocols. AS1, AS2, AS3 - The AS1 Protocol AS1, AS2, AS3 - The AS1 Protocol (Enterprise only)

Automize as2