Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should websockets be enabled by default? #6196

Open
manics opened this issue Dec 12, 2019 · 1 comment
Open

Should websockets be enabled by default? #6196

manics opened this issue Dec 12, 2019 · 1 comment

Comments

@manics
Copy link
Member

manics commented Dec 12, 2019

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.

@joshmoore
Copy link
Member

No objection, but I'd put this after the general 5.6 release blockers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants