Forum Index » Browser development » Secure websocket   XML
 
Author Message
Richard3



Joined: 17/04/2018 04:27:59
Messages: 0
Offline

Can you give some documentation on using secure websocket connection to the Jabra websocket service? My use case is I want to connect from the local browser to the locally installed service.

I see you can specify the certificate thumbprint at installation time. But what should this thumbprint be?

I tried just using wss: but that didn't work.

Please give detailed steps so I can get this working. As you probably know, browsers will block non-secure ws connections from a https page so this is critical to a useful real-world application.
Mehmet



Joined: 17/04/2018 04:27:59
Messages: 1
Offline

Hi Richard,
let me see if we can prepare a step by step procedure for your purpose. Stay tuned for an update (within a weeks time).

Thanks.
Regards
Mehmet
Richard3



Joined: 17/04/2018 04:27:59
Messages: 0
Offline

Cool Mehmet. I look forward to it.
smilie Richard.
Mehmet



Joined: 17/04/2018 04:27:59
Messages: 1
Offline

Hi Richard, after digging more into the situation, unfortunately Jabra do not provide a certificate which you can install. So for your purpose I recommend you to create your own certificate and install it to your 'Windows certificates store' and also to remember importing the certificate in the browser e.g. when used with Google Chrome.
Hopefully below link can be helpful:
http://stackoverflow.com/questions/8169999/how-can-i-create-a-self-signed-cert-for-localhost

Look forward to hear from you.

Thanks
Mehmet
Richard3



Joined: 17/04/2018 04:27:59
Messages: 0
Offline

Hi Mehmet,

Well that is a totally disappointing answer. Our software is deployed b2b, not as part of enterprise infrastructure so expecting our clients to generate and install a certificate on their machine is laughable.

I was excited for your initiative to enable web socket access to your headsets... but now when it comes to a real-world application and not just a demo, the details make it impractical.

Is that the best you can do?

Sincerely,
Richard.
Mehmet



Joined: 17/04/2018 04:27:59
Messages: 1
Offline

Hi Richard,
thank you for the point and input. Some external partners/developers have already publicly released their solution containing our WebSocket SDK, and the wss certificate question have popped up before with the outcome of the partner already having/developing the certificate themselves.

Of course there is always another way. Let me see if a workaround can be offered.

Have a nice day.

Regards
Mehmet
Anders2



Joined: 17/04/2018 04:27:59
Messages: 0
Offline

Hello Mehmet,

I am having the same issue, and I would like to know if you have made some kind of service or do I still need to make my own certificate?
Mehmet



Joined: 17/04/2018 04:27:59
Messages: 1
Offline

Hi Anders,
we released version 1.2.393.0 in December which include a certificate during installation. Please have a look at the new package and let me know if you have further questions in its usage. thanks
Anders2



Joined: 17/04/2018 04:27:59
Messages: 0
Offline

I am using the new version, but what is "localjabrawebsocketserver" in wss://localjabrawebsocketserver:8080?

The demo you provided also uses localjabrawebsocketserver, but it's not working.
Mehmet



Joined: 17/04/2018 04:27:59
Messages: 1
Offline

Hi Anders, the localjabrawebsocketserver is the jabra 'server' module that handle the communication from the browser to the headset itself. Recently browsers like Chrome stopped supporting direct 'localhost' signalling, which we have solved through the jabrawebsocketserver and the certificate included in the updated package.

Hope this clarifies this. Please let me know the issue you are observing with the demo tool.

Thanks.
Anders2



Joined: 17/04/2018 04:27:59
Messages: 0
Offline

I hear you, and it's smart, but when I write that it's not working.. What shall I write?
If I test it in yout test, it's still not working: https://jabra-webrtc.azurewebsites.net/
Mehmet



Joined: 17/04/2018 04:27:59
Messages: 1
Offline

Ok Anders, can you please elaborate on what is not working? Does the browser not detect whether the Websocket application is running? Is the Websocket application installed and launched prior to trying the Test client html page? Or is the problem something else.
Alternatively please try enabling debug log on the websocket client (section 1.2.3) in the document included in the SDK.

Thanks.
Anders2



Joined: 17/04/2018 04:27:59
Messages: 0
Offline

Yes the Websocket application is installed and is working fine on HTTP with localhost, but as soon as I change localhost to wss://localjabrawebsocketserver:8080, it's not working...

My question is this: What shall I write insted of wss://localjabrawebsocketserver:8080?
And is the new Websocket app from you ment to be plug and play?
Mehmet



Joined: 17/04/2018 04:27:59
Messages: 1
Offline

During the investigation something odd showed up, perhaps this is the same as what you have reported. We will look into this this week and hopefully provide an update soon. I will let you know as soon as i have something you could evaluate.
Thank you Anders.
Mehmet



Joined: 17/04/2018 04:27:59
Messages: 1
Offline

Hi Anders,
the problem you have had should now be solved. The issue was that the demo tools was pointing and using old Websocket installers. Hope its possible for you to retry and confirm that your observations are no longer present.

Thanks.
 
 
Go to: