Microsoft KB Archive/196321

= Partner's VeriSign Encryption Certificate Shown as Signature Certificate =

Article ID: 196321

Article Last Modified on 7/14/2004

-

APPLIES TO


 * Microsoft Site Server 3.0 Commerce Edition

-



This article was previously published under Q196321



SYMPTOMS
VeriSign encryption certificates included with imported partner trading profiles may be designated with a "Usage:" of "signature" on the Properties page for the certificate. This incorrect designation is only apparent from the importing partner's Commerce Interchange Pipeline Manager interface. This incorrect designation has no impact on the actual functionality of the VeriSign certificate between trading partners.



CAUSE
Commerce Interchange Pipeline Manager has no way of detecting whether VeriSign certificates imported with partner trading profiles are signature or encryption, and therefore will always display a "Usage:" of "signature." This limitation is not apparent when you use certificates created with Microsoft Certificate Server and imported with partner trading profiles. Certificates created with Microsoft Certificate Server and imported with partner trading profiles display the correct usage as viewed from the importing partners Commerce Interchange Pipeline Manager interface.



STATUS
Microsoft has confirmed this to be a problem in Site Server 3.0, Commerce Edition.

Additional query words: CIPM

Keywords: kbbug kbpending KB196321

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.