Urgent Help required to fix this error "An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail."
-
Hi , We are trying to implement Java WebService in .Net . But getting error like An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. We registerd the security certificate everything but still getting this issue . The issue what we found is we are getting X509IssuerSerial alias: null in xml request generated by .Net application Can any one please guide how to sort out this issue. the app.config is as follows <?xml version="1.0" encoding="utf-8" ?> <configuration> <system.serviceModel> <client> <endpoint address="http://localhost:1919/testWs/services/HelloWorld" behaviorConfiguration="ClientCertBehavior" binding="customBinding" bindingConfiguration="JavaInterop" contract="localhost.HelloWorldPortType" name="HelloWorldHttpSoap12Endpoint"> <identity> <dns value="YALAMANCHILI" /> </identity> </endpoint> </client> <bindings> <customBinding> <binding name="JavaInterop"> <security defaultAlgorithmSuite="Basic128Rsa15" allowSerializedSigningTokenOnReply="true" authenticationMode="MutualCertificate" requireDerivedKeys="false" securityHeaderLayout="Lax" includeTimestamp="true" messageProtectionOrder="EncryptBeforeSign" messageSecurityVersion="WSSecurity10WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10"> <issuedTokenParameters keyType="AsymmetricKey"> <issuer address="" binding="customBinding" bindingConfiguration="JavaInterop" /> <issuerMetadata address=""> <identity> <certificateReference x509FindType="FindByIssuerName" isChainIncluded="false" /> </identity> </issuerMetadata> </issuedTokenParameters> <localClientSettings detectReplays="false" /> <secureConversationBootstrap defaultAlgorithmSuite="Basic128Rsa15" allowSerializedSigningTokenOnReply="true" authenticationMode="MutualCertificate" requireDerivedKeys="false" securityHeaderLayout="Lax" messageProtectionOrder="EncryptBeforeSign"> <is
-
Hi , We are trying to implement Java WebService in .Net . But getting error like An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. We registerd the security certificate everything but still getting this issue . The issue what we found is we are getting X509IssuerSerial alias: null in xml request generated by .Net application Can any one please guide how to sort out this issue. the app.config is as follows <?xml version="1.0" encoding="utf-8" ?> <configuration> <system.serviceModel> <client> <endpoint address="http://localhost:1919/testWs/services/HelloWorld" behaviorConfiguration="ClientCertBehavior" binding="customBinding" bindingConfiguration="JavaInterop" contract="localhost.HelloWorldPortType" name="HelloWorldHttpSoap12Endpoint"> <identity> <dns value="YALAMANCHILI" /> </identity> </endpoint> </client> <bindings> <customBinding> <binding name="JavaInterop"> <security defaultAlgorithmSuite="Basic128Rsa15" allowSerializedSigningTokenOnReply="true" authenticationMode="MutualCertificate" requireDerivedKeys="false" securityHeaderLayout="Lax" includeTimestamp="true" messageProtectionOrder="EncryptBeforeSign" messageSecurityVersion="WSSecurity10WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11BasicSecurityProfile10"> <issuedTokenParameters keyType="AsymmetricKey"> <issuer address="" binding="customBinding" bindingConfiguration="JavaInterop" /> <issuerMetadata address=""> <identity> <certificateReference x509FindType="FindByIssuerName" isChainIncluded="false" /> </identity> </issuerMetadata> </issuedTokenParameters> <localClientSettings detectReplays="false" /> <secureConversationBootstrap defaultAlgorithmSuite="Basic128Rsa15" allowSerializedSigningTokenOnReply="true" authenticationMode="MutualCertificate" requireDerivedKeys="false" securityHeaderLayout="Lax" messageProtectionOrder="EncryptBeforeSign"> <is
I also have this problem, I think there's wrong w/ how you use the service, not the service itself.