You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's had quite a lot of testing, and most of the clients (Python, Java) wil support it by the time 5.6 is released. Should we enable websockets (wss i.e. "secure" only) by default in the server, and provide an east config option in the generated OMERO.web nginx config?
Note for Nginx to proxy wss OMERO will need a self signed certificate (or even better, an official certificate even though it won't be verified by clients) with a supported cipher i.e. not anon-DH as is currently used for omero ssl.
The text was updated successfully, but these errors were encountered:
It's had quite a lot of testing, and most of the clients (Python, Java) wil support it by the time 5.6 is released. Should we enable websockets (wss i.e. "secure" only) by default in the server, and provide an east config option in the generated OMERO.web nginx config?
Note for Nginx to proxy wss OMERO will need a self signed certificate (or even better, an official certificate even though it won't be verified by clients) with a supported cipher i.e. not anon-DH as is currently used for omero ssl.
The text was updated successfully, but these errors were encountered: