I have a JavaScript client that uses the Guacamole.Client (guacamole-common-js class) and I would like to directly connect to guacd avoiding the tunneling through a server (like they do in the example).
So I need to pass the parameters like the ip and port of the RDP-host, username and password etc. from the JavaScript client to the guacd proxy and open the connection.
For anyone who may be interested, I found a (sort of) workaround:
I couldn't find a way to connect from the Javascript client directly but I found an alternative to the server side Java servlet. It's an npm package called guacamole-lite. With that, you can tunnel your request through a node js backend.
Related
My backend is built in express with socket.io and my frontend in plain js.
How is it possible to have them in different projects (in different repos on github) but still have them work together (that the client knows where the server is so to say)?
Do I have to sync them somehow?
You can put them in different repositories. The client will communicate with the server using its url.
When you run the server it is on a specific host (any address like localhost or any ip or domain plus a port). The client just need to know this hostname and port.
I have configured my Vert.x server built in Java to already handle HTTP connections properly, but I would like to add an additional layer of security through HTTPS. I use the standard fetch call to make POST requests to the server. I have searched through the Vert.x documentation already, but the only information I can find is if I use Vert.x as client code as well, but I would like to avoid that if possible. Is there a way to configure my client and server to work together to form a secure connection without having to build an encryption schema from scratch?
If I understood you correctly, you have but one VertX instance, without load balancer, and you would like to access it using HTTPS protocol.
It doesn't actually matter whether you access it through
When starting your VertX server, make sure you specify setSSL(true) and all the other arguments:
https://github.com/vert-x/vertx-examples/blob/master/src/raw/java/https/ServerExample.java#L39
I had to perfrom a mutual authentification with certificate between a Javascript client and a Server running with TomCat
I change the configuration of my server so it will find the trust/keys store
But for the client part,i found many exemples with a JAVA client using the javax.net.ssl to define parameters (keyStore/Truststore) but i did not found anything for a JavaScript Client
is it Possible and how i can do it?
Thanks a lot!
I am using websockets in javascript and python flask.
I have a websocket server to which i connect my webpage using javascript websockets. The "/" contains a form that contain the ip address of the websocket server, and "/connectToServer" route will establish a websocket connection with the server.
Now, I will have routes from this webpage like, /details, /profile. I need to use the same instance of the websocket in all my routes. How do i do it?
P.S. I do not intend to use the websocket client api in python. I need to do it in javascript only.
You would need something to make your page persistent.
Client-side libraries such as Angular or Vue (just two random examples) will do the job.
However you should look into a tutorial or something since its not very straightforward
Im looking form something to make socket connection between client, without pass through the server. Is there any node package to do this?. Server only send the other client socket, and the clients recieve and send data to each other..
Or, how can we make the implamantation. We need to make a server in client side, but we dont have node installed in the client..
The closest thing that currently exists in some form is not currently part of socket.io. It is called WebRTC and is implemented in Chrome currently. It allows the browser to connect with other browsers.
http://www.webrtc.org
The question is what kind of application is your client? If you are talking about ordinary webbrowsers you need to think about writing pluings (tough case).
If you are talking about clients you have more control then you should look at technique Puching the hole exploited by Skype or P2P apps.
http://it.slashdot.org/story/06/12/15/191205/how-skype-punches-holes-in-firewalls
In general the server is used for TCP sockets orchestration the acutall comunication go directly.