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

Remove auto-fallback to HTTP comms. #2204

Closed
hjoliver opened this issue Mar 12, 2017 · 3 comments · Fixed by #2355
Closed

Remove auto-fallback to HTTP comms. #2204

hjoliver opened this issue Mar 12, 2017 · 3 comments · Fixed by #2355
Assignees
Milestone

Comments

@hjoliver
Copy link
Member

hjoliver commented Mar 12, 2017

From @dpmatthews:

Python OpenSSL is required to use HTTPS. Otherwise cylc falls back to HTTP and issues lots of warnings (so it's not really very usable). I think we should:

  • Allow [communication] method = http (only option at the moment is https) (assuming we want to support this).
  • Add tests to make sure it works.
  • Modify cylc check-software to test for OpenSSL (unless HTTP option configured).
  • Get rid of the fall-back - i.e. fail if you've configured https method but can't use it.

Also:

  • document the OpenSSL dependency
@hjoliver hjoliver added this to the later milestone Mar 12, 2017
@hjoliver
Copy link
Member Author

hjoliver commented Mar 27, 2017

Current fallback is imperfect too. Without HTTPS/SSL support job submission to a remote host fails with SuiteServiceFileError: Couldn't get ssl.cert.

Which contradicts current documentation of "By default, the communication method is HTTPS secured with HTTP Digest Authentication. If the system does not support SSL, it will fall back to HTTP."

@chanwilson
Copy link

There's also a typo in the CUG in section 12.4; [communications] vs [communication]

@hjoliver
Copy link
Member Author

hjoliver commented Apr 3, 2017

There's also a typo in the CUG in section 12.4; [communications] vs [communication]

Fixed: 2e2ddd0

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

Successfully merging a pull request may close this issue.

5 participants