-
Notifications
You must be signed in to change notification settings - Fork 575
vnc authentication seems to be not working #1231
Comments
Zalenium already supports basic auth. You shouldn’t need to be modifying any nginx config. You just need to enable the basic auth support in Zalenium. See https://opensource.zalando.com/zalenium/ |
That I've already enabled and it works Ok, but it does not protect |
Oh that's interesting. Will leave this open then. I'm sure you are aware that development has stopped on this project, so it isn't going to be fixed on its own. |
Ok, I am aware of that, I was hoping that someone from the team or anyone who knows what's the problem can give me some hints perhaps I could fix it myself, I've already made a couple of small modifications in the Zalenium. |
Hi,
I am trying to secure the VNC traffic by Nginx's secure_link_module or something like that, after finding it not working I tried to understand what's the problem then I see that
VncAuthenticationServlet
implemented to do the authentication, but it seems that it does not receive/check the requests.So based on the Nginx config (below) all the requests to
proxy/ip:port/websockify
should be authenticated byVncAuthenticationServlet
, I put a couple ofLOGGER.info
calls to see how can I customize it for my own purpose, but no logs were captured.Please help me figure out if this part is not working at all or I'm missing something here.
It worth mentioning that the Zalenium is hosted inside Kubernetes the noVNC client works perfectly through HTTPS (WSS).
The text was updated successfully, but these errors were encountered: