A call to SSPI failed, see inner exception. The message received was unexpected or badly formatted

Question

1.00/5 (1 vote)

See more:

1. We have Web-socket Server application (java [Linux] - TLS12)
2. Java Client application(java client library)
3. Dot net client application (Dot net client library - Net 4.5.2)

We are able to connect to web-socket server app through java client library without any issue, But we are getting the following exception when we trying to connect using dot net client library:

Quote:
Error Details :
"A call to SSPI failed, see inner exception. The message received was unexpected or badly formatted"

Stack trace :
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
at SuperSocket.ClientEngine.SslStreamTcpSession.OnAuthenticated(IAsyncResult result)

What I have tried:

1. System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
2. As it is working from the java client library, there should not be any issue with certificate in server.

Pls help, Thanks in advance.

Posted 30-Aug-17 10:25am

raveendranath

Updated 4-Sep-17 20:26pm

Graeme_Grant

v5

Add a Solution

Comments

Richard MacCutchan 31-Aug-17 3:30am

The error message is telling you which part of the request caused the eroro. You just need to inspect it to see why.

raveendranath 31-Aug-17 5:04am

I just tried to open the connection, did not send any content.

See following code

client = new WebSocket(wsClientImpl.Url, SslProtocols.Tls12.ToString() , null, authorizationHeaderItems, "","", WebSocketVersion.None);
client.Open();

Richard MacCutchan 31-Aug-17 5:24am

Look at the error message: "The message received was unexpected or badly formatted". So wherever you are sending this message, the receiver is either not expecting it, or what you are sending is in the wrong format.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

raveendranath · Answer 1 · 2017-09-04T20:26:00

Solution 1

1.Updated WebSocket4Net.dll to

0.15.0-beta6

2.Changed code as following

websocket = new WebSocket4Net.WebSocket(URL,
          sslProtocols: SslProtocols.Tls12 | SslProtocols.Tls11 | SslProtocols.Tls,
          customHeaderItems : authorizationHeaderItems);

It worked for me.

Posted 4-Sep-17 20:26pm

raveendranath