|
Home > Archive > BizTalk Server General > November 2004 > SMIME encryption algorithm
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SMIME encryption algorithm
|
|
| jeremy 2004-11-19, 7:46 am |
| We have a client the is using our public key to encrypt an xml message using
openssl. Is there a specific encryption algorithm they need to use for
BizTalk 2002 to sucessfully decrypt? Are there any known compatibility issues
with openSSL and biztalk?
When I use BizTalk to decrypt the message SMIME message using our private
key, the message gets suspended saying "no parser component recognized ...."
So I believe that biztalk has sucessfully recognized my private/public key
pair, but something has gone wrong in the decryption as the xml is not
decoded and when I look in the suspended queue all i see our the SMIME
headers with no message body.
Anyone have any suggestions? The message headers they are providing are as
follows. What is the minimum they need to provide?
MIME-Version: 1.0
Content-Disposition: attachment; filename="smime.p7m"
Content-Type: application/x-pkcs7-mime; name="smime.p7m"
Content-Transfer-Encoding: base64
If I use biztalk to encrypt with our public key and decrypt with our private
key everything works fine......
| |
| jeremy 2004-11-19, 7:46 am |
| more specifically, does biztalk support the following excryption algorithms:
DES (56 bits), triple DES (168 bits)
RC2 (40, 64 or 128 bit)
AES (128, 192 or 256 bit)
"jeremy" wrote:
> We have a client the is using our public key to encrypt an xml message using
> openssl. Is there a specific encryption algorithm they need to use for
> BizTalk 2002 to sucessfully decrypt? Are there any known compatibility issues
> with openSSL and biztalk?
>
> When I use BizTalk to decrypt the message SMIME message using our private
> key, the message gets suspended saying "no parser component recognized ...."
> So I believe that biztalk has sucessfully recognized my private/public key
> pair, but something has gone wrong in the decryption as the xml is not
> decoded and when I look in the suspended queue all i see our the SMIME
> headers with no message body.
>
> Anyone have any suggestions? The message headers they are providing are as
> follows. What is the minimum they need to provide?
>
> MIME-Version: 1.0
> Content-Disposition: attachment; filename="smime.p7m"
> Content-Type: application/x-pkcs7-mime; name="smime.p7m"
> Content-Transfer-Encoding: base64
>
> If I use biztalk to encrypt with our public key and decrypt with our private
> key everything works fine......
>
| |
| Balaji Thiagarajan 2004-11-22, 5:48 pm |
| Jeremy:
BizTalk Server 2004 supports public key encryption of outbound messages and
decryption of inbound messages based on Secure Multipurpose Internet Mail
Extensions (S/MIME). BizTalk Server uses S/MIME version 3 for encryption of
outbound messages, and S/MIME versions 2 and 3 for decryption of inbound
messages.
BizTalk Server supports RSA and Diffie Hellman encryption certificates.
BizTalk Server supports Data Encryption Standard (DES), 3DES, and RC2
encryption algorithms.
--
Balaji Thiagarajan
MCP (BizTalk)
http://biztalkbits.blogspot.com
--
"jeremy" <jeremy@discussions.microsoft.com> wrote in message
news:73D08B37-0B27-461F-A4A3-D7650C41CBE5@microsoft.com...
> more specifically, does biztalk support the following excryption
algorithms:[vbcol=seagreen]
>
> DES (56 bits), triple DES (168 bits)
> RC2 (40, 64 or 128 bit)
> AES (128, 192 or 256 bit)
>
>
> "jeremy" wrote:
>
using[vbcol=seagreen]
issues[vbcol=seagreen]
private[vbcol=seagreen]
....."[vbcol=seagreen]
key[vbcol=seagreen]
as[vbcol=seagreen]
private[vbcol=seagreen]
|
|
|
|
|