Encrypted or Signed Non-XML Docs Require AutoSMIME (202020)


The information in this article applies to:

  • Microsoft Site Server 3.0 Commerce Edition
This article was previously published under Q202020

SUMMARY

Commerce Interchange Pipeline Manager transmit profiles can be configured with several different signature and/or encryption components. If a transmit profile is used to send a signed and/or encrypted non-XML business document to a standard receive location on another Commerce Server, then the transmit profile must be configured as follows:

For non-XML documents to be digitally signed: Digitally signed outgoing non-XML documents must use a transmit profile configured with the AutoSMIME or EncodeSMIME signature component if bound for a standard receive location.

For non-XML documents to be digitally encrypted: Use a transmit profile configured with the AutoSMIME security component if bound for a standard receive location.

For non-XML documents to be digitally signed and encrypted: Use a transmit profile configured with the AutoSMIME security component if bound for a standard receive location.

The signature and encryption options selected when you configure a transmit profile for an outgoing business document can be viewed in the Commerce Interchange Pipeline Manager as follows:
  1. Open the trading partners Transmit Profiles folder.
  2. Double-click on the designated receive location.
  3. Click the Security tab.
  4. Under Signature component, click the drop-down list to view the following available components:

    None
    DigitalSig (Sign PKCS)
    DigitalSigAuto (Auto Sign PKCS)
    EncodeSMIME (Sign & Encrypt SMIME)
    EncodeSMIMEAuto (Auto Sign & Encrypt)
    Scriptor (VB/JavaScript)

  5. Under Encryption component, click the drop-down list to view the following available components:

    None
    EncryptPKCS(Encrypt PKCS)
    EncryptPKCSAuto (Auto Encrypt PKCS)
    Scriptor (VB/Java Script)

Multiple signature and encryption components are available for developers who want to write a custom receive location that will understand signature or encryption schemes, other than EncodeSMIME.

MORE INFORMATION

If an outgoing agreement is configured with a transmit profile that uses a standard receive location and a digital security component other than AutoSMIME or EncodeSMIME and configured with a non-XML document, attempts to send the non-XML document will fail with the following error on the sending Commerce Server:
Outgoing Agreement Component Misconfigured. The pipeline associated with the outgoing agreement failed due to a component configuration problem.
On the receiving Commerce Server, the following error is logged in the server's application log:
Event ID: 2101
Source: CIPM
Type: Error
Category: None
Description:
RECEIVE FAILURE - Incoming Security PKCS Decryption Failure

The PKCS component failed to decrypt the incoming business document.

HRESULT = 0x80040835

Location Name =
Location Type =
Logging Type = Append

Incoming Agreement = Undetermined

DETAIL - (0x80070057) The parameter is incorrect.
Modification Type:MajorLast Reviewed:6/24/2004
Keywords:kbinfo kbnofix KB202020
©2004 Microsoft Corporation. All rights reserved.