I have build and deployed the application onto my local testing machine that has Biztalk Server 2010 developer edition 32-bit installed and running.

in the sample biztalk application i used the new pipeline "I called it XMl Signer after the component provided".

Restarted the host instance, started the application again and put sample xml file in the folder that had already receive handler configured to read from.

The errors shown in the application event view are:

1. EventData: Searching for installed BizCrypto addons. Type: Information
2. EventData: No addons found (the exact message: BizCrypto.BizTalk.Addons. Could not load file or assembly 'BizCrypto.BizTalk.Addons, Version=9.1.216.0, Culture=neutral, PublicKeyToken=5a62fa96d0ac431a' or one of its dependencies. The system cannot find the file specified.) Type: Information

3. EventData: You are using trial version of BizCrypto. All the major functionality is a subject for the following EVALUATION LIMITATIONS : - opaque DELAYS of up to 1.5 seconds per atomic operation make the components work SLOWER than they do, - the number of components' invocations is limited by 50 per single BizTalk host instance. Please consider purchasing a license to get rid of the above limitations. You can also request a time-limited non-evaluation license key, which removes the evaluation restrictions using the web form on http://www.eldos.com/bizcrypto/keyreq/ Type: Warning

the message has been suspended and not processed properly. I understand the warning is due to not licensed version but the rest i cannot follow. The process is to use the private key to sign the XML file and the result would an addition of an elelmet < signature > to the end of the xml file, right?

Can you provide a sample bistalk application that implements the XML signer and verifier Pipeline components?

I have gone through the documentations provided but seems that i am missing something here. I suspect:
- using a wrong certificate file. ( the concept of private key exported file)
- some attributes need to be configured to generate and XMLdsig compliant signed xml files.

Yes Signature Method is set to RSASHA1
SignatureMethodType is set to Signature
SignatureType = Enveloped

I think I have an issue with the file itself. I have created the certificate using Makecert utility and exported it with private key to a .pfx file. just to confirm, I need the file to contain private key to do the signing, correct?

I think I have an issue with the file itself. I have created the certificate using Makecert utility and exported it with private key to a .pfx file. just to confirm, I need the file to contain private key to do the signing, correct?

Dear support,
I still cannot configure the XML Signer. I created a pfx file and used in the test application and I always get incorrect secret key... how can you help me? I want to buy the professional version but I need a proof that it works. I need an online support or chat to discuss what have I have done wrongly

I am really sorry about the confusion. We ran several checks on our side, and tracked the issue down to a mistake in the pipeline component that prevents it from loading RSA certificates correctly. We've managed to fix it and prepared a correct pipeline assembly for you. I'll create a Helpdesk ticket for you to send you the updated assembly through.

Please create a ticket in our Helpdesk system, and we will upload the correct assembly there. BTW, if you have a BizCrypto license, please assign your license ticket to your web site account so that we could identify you as a customer and provide you a faster support.

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.