Urgent…Https Send Port Problem

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Urgent…Https Send Port Problem

Viewing 1 reply thread
  • Author
    Posts
    • #18335

      hi everybody,

      i have the below case for a current project and i kindly need some help.

      – i have a Http send port that should post a message to an SSL secured address (https://somesite.com)

      – i have the client certificate (public key) of the target server (somesite.com). i have installed the certificate in the personal store of the user account running the BizTalk host instance. the CA of the client certificate is also stored in the trusted root CAs.

      – i copied the client certificate thumbprint and pasted it in the "SSL client certificate thumbprint" property of the Http Send Port.

      in my understanding i have done everything correctly, however once i post the message i get the following error:

      "The underlying connection was closed. Could not establish trust relationship for the SSL/TLS secure channel"

    • #18348

      I could be off base, but do you have a party set up in your App with that cert selected?  That caused me problems when I was first working with BT and certs.  Other than that, I do not know much about ssl.

       

      good luck

      • #18354

        thnx for the reply,

        no i do not have the case you mentioned. i still cannot find the source of the problem.

        • #18357

          The source of the problem could be the location of the certificate, i.e. for the sen port the certificate should be located in “Other People” store on the computer running the BizTalk Server. Also, you have to enable mime encryption. There comes a white paper:
          http://msdn2.microsoft.com/en-gb/library/ms865024.aspx

          All the best,
          Tudor Cristea

          • #18363

            Tudor, thnx for the reply,

            the case you are talking about is when using custom pipelines with MIME encoding component…this is not my case. i know from MSDN that what i should do is to install the client certificate in the personal store and add the thumbprint to the send port. however i still cannot find the problem.

            just a hint: the client certificate i have is the public key of the server i am trying to talk to. in my understanding of authentication, should this not be the server’s private key in order for the server to authenticate me?

            • #18388

              Here comes a simpler article – nevertheless better than the one from msdn: http://www.topxml.com/rbnews/BizTalk%202006/re-56948_Building-a-Complete-Certificate-Scenario-With-BizTalk-Server-2006.aspx

              I have had the same problem and after some four hours of struggle it works as in this article – you can skip the send/receive pipelines, just make your certificate as stated there and follow the exports.

              You should pay great attention to the names: I’ve been creating a certificate with the name “WinLaptop” in the makecert command (the CN portion). Then I set the send port url to https://WinLaptot/….. The the public key (the cer thing) i have imported in “Other People” (the thumbprint way did not work for me and i don’t really care why). The private key (the pfx thing) you can use in IIS to create a secure site. You do that by importing the private key with defaults, then you will see the certificate when you try t-up the SSL on the default web site. Again, mind the names: if they don’t match, then will not work. I am using name in my router record to solve the name. A DNS server will be better. Don’ t try localhost or IP address, will not work.

              If you make your own certificate, the public key must be imported in the Trusted Root Certificate Authorities store, for the Current User. For a certificate you got from someone else, open it first and see if is trusted. If not, the do the same.

              To answer your question: you need the public key, the one that you use to encrypt the message. The private key is needed by the server.

              I was to reply to the message, but I got too much to do over the weekend. Now is fixed and I hope you will enjoy.

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.