Generally, it is not recommended to store passwords in the binding file and by default BizTalk administration UI clears it out when exporting binding to the xml file. But in development environment where you have automated continuous integration build and deployment not having password in the binding file will prevent application from starting and CI process fail. It can become tedious in staging deployments (TEST, UAT) as well, especially if you have multiple endpoints that use accounts with passwords. ......
Recently, while debugging desktop client - WCF service application I came across this error: System.ServiceModel.Securit... was caught Message=”An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.” Source=”mscorlib” StackTrace: Server stack trace: at System.ServiceModel.Channel... reply, SecurityProtocolCorrelation... correlationState, ......