none
WSDL TLS 1.2 Session ID =0 RRS feed

  • Question

  • Имею wsdl файл который проверил в ReadyAPI на работоспособность, работает.
    для С Sharp wsdl преобразовал в cs:

    svcutil.exe D:\GenericTicketConnector.wsdl /wrapped /serializer:XmlSerializer /t:code /l:c# /o:"D:\OTRS5.cs" /n:*,NamespaceName

    use

    var endpoint = new EndpointAddress("https://****/otrs/nph-genericinterface.pl/Webservice/GenericTicketConnector");
    var binding = new BasicHttpBinding();
    System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
              
    binding.Security.Mode = BasicHttpSecurityMode.Transport; 
     
                NamespaceName.GenericTicketConnector_PortTypeClient g = new NamespaceName.GenericTicketConnector_PortTypeClient(binding, endpoint);
    NamespaceName.SessionCreate sc = new SessionCreate();
    sc.Item = "****";
    sc.ItemElementName = NamespaceName.ItemChoiceType8.UserLogin;
    sc.Password = "****";
    var f = g.SessionCreate(sc);

    the response from the service is not receiving however. in WireShark I see activity and I observe such defect, that at a packet "Client Hello" parameter Session ID is 0 and from here all failure.
    tell me where and why this is happening and how to fix it?

    https://prnt.sc/ienj1t


    • Edited by Magals Thursday, February 15, 2018 12:43 PM
    Thursday, February 15, 2018 12:42 PM

All replies

  • I don't understand your question. What you posted isn't a WCF response but rather the SSL handshaking which shouldn't matter. Is your SessionCreate method returning back the correct data? If not then post what the differences are. The SSL handshaking doesn't matter provided the connection is successful. If you're getting an SSL handshaking error then please post the exception details around it.

    Michael Taylor http://www.michaeltaylorp3.net

    Thursday, February 15, 2018 4:03 PM
    Moderator
  • I don't understand your question. What you posted isn't a WCF response but rather the SSL handshaking which shouldn't matter. Is your SessionCreate method returning back the correct data? If not then post what the differences are. The SSL handshaking doesn't matter provided the connection is successful. If you're getting an SSL handshaking error then please post the exception details around it.

    Michael Taylor http://www.michaeltaylorp3.net

    no exception signal. returns the object whose fields are null.
    I think it's because of a wrong connection. Since through the ReadyApi program, it is possible to obtain the result of the function.

    https://prnt.sc/if7ngs

    Thursday, February 15, 2018 5:50 PM
  • If the fields are null then it is most likely a request issue where you're not passing the data it expects. If it were a handshaking issue or anything like that then you'd get an exception. 

    Run Fiddler and monitor your request going across the wire. You should be able to look at the request and response and verify they are correct. If the response isn't correct for the request then you can use SoapUI or Postman or similar (depending upon your binding) to play around with the request until it returns the response you expect.

    My gut instinct is that the issue is on the server side. You'd have to debug the server code to know for sure though.


    Michael Taylor http://www.michaeltaylorp3.net

    Thursday, February 15, 2018 6:09 PM
    Moderator
  • Hi Magals,

    Is there any update? have you resolved the issue?

    Best regards,

    Zhanglong


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, February 26, 2018 8:24 AM
    Moderator