Clever Geek Handbook

BizTalk SOAP Port Password in Binding File

I inherited a BizTalk 2006 application that uses multiple SOAP ports to request data from a third party web service. The web service is protected by "basic" authentication - username / password. After making a few improvements to an application that I have deployed to a test integration server that has access to a third party web service. The BizTalk application was unable to receive data and I soon realized that I forgot to provide the username / password on the SOAP send ports. I wanted the deployment of the BizTalk application to be as automatic as possible, since I cannot be present when it is deployed to a real server. I opened the bind file, posted the 1st of the problematic SOAP send ports and searched for* which BizTalk uses to replace the password, except that it isn't! It seems the password for SOAP ports is set to NULL and not * , see here for more information: http://msdn.microsoft.com/en-us/library/aa547319.aspx

I kept updating the binding, but when I came to check, after importing my fixed binding file, I found that I was having the same problem as before. I have double checked and can confirm that the correct password is now present in the binding file, but although BizTalk does not complain during the import, I get the following exception when starting the application:

Details: "ArgumentNullException: String reference not set to string instance. Parameter name: s".

If you then manually change the password through the BizTalk Admin Console, everything will work fine.

Someone else had a similar problem with bindings for a SOAP port - does anyone have a solution?

0


source to share


2 answers


In the past, I've been something like this. The password is entered as "****". Good. I would not want all my secrets to be exported to a bind file. What do you get when you export the bindings and you leave the password NULL. The Variable Type (vt) attribute for the XML element for password is set to vt = "1", which is NULL. It doesn't matter what you enter for the password. It might even cause the error you described. I would suggest that you include a copy of the XML document for validation.



+3


source


I've never seen this problem before - I do exactly what you are trying to do and it works great.

I've included the <TransportTypeData> element from one of my BizTalk bindings that works. Hope it helps to compare with something.



<TransportTypeData>
&lt;CustomProps&gt;
&lt;AuthenticationScheme vt="8"&gt;Basic&lt;/AuthenticationScheme&gt;
&lt;AssemblyName vt="8"&gt;WebService.ProxyClass, Version=1.0.0.0, 
Culture=neutral, PublicKeyToken=xyz&lt;/AssemblyName&gt;
&lt;Username vt="8"&gt;soapUser&lt;/Username&gt;
&lt;UseProxy vt="11"&gt;0&lt;/UseProxy&gt;
&lt;UseSoap12 vt="11"&gt;0&lt;/UseSoap12&gt;&lt;UsingOrchestration vt="11"&gt;0&lt;/UsingOrchestration&gt;
&lt;UseSSO vt="11"&gt;0&lt;/UseSSO&gt;
&lt;Password vt="8"&gt;MYPASSWORD&lt;/Password&gt;
&lt;ProxyPort vt="3"&gt;80&lt;/ProxyPort&gt;&lt;AssemblyPath
vt="8"&gt;C:\ProxyClass\bin\Debug\ProxyClass.dll&lt;/AssemblyPath&gt;
&lt;TypeName vt="8"&gt;ProxyClass.Webservice.servicesService&lt;/TypeName&gt;
&lt;MethodName vt="8"&gt;PickupRequest&lt;/MethodName&gt;
&lt;UseHandlerSetting vt="11"&gt;-1&lt;/UseHandlerSetting&gt;
&lt;/CustomProps&gt;
</TransportTypeData>
0


source






More articles:


All Articles