Project

General

Profile

Bug #34667

Add SSL support when connecting to mqtt broker

Added by Adam Ruzicka 3 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Smart Proxy - SSH

Associated revisions

Revision fc0b7856 (diff)
Added by Adam Růžička 3 months ago

Fixes #34667 - Add SSL support when connecting to mqtt broker (#75)

Use of SSL can be forced either way by explicitly setting mqtt_tls
setting. If unset, it gets used if certificate, private key and CA
certificate are available. Currently it reuses the foreman_ssl_* set
of certs the smart proxy has.

Revision 3e89c35f (diff)
Added by Adam Ruzicka about 1 month ago

Refs #34667 - Fall back to server set of certs

in case client certs are not configured

History

#1 Updated by The Foreman Bot 3 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/75 added

#2 Updated by The Foreman Bot 3 months ago

  • Fixed in Releases smart_proxy_remote_execution_ssh-0.5.3 added

#3 Updated by Anonymous 3 months ago

  • Status changed from Ready For Testing to Closed

#4 Updated by Adam Ruzicka 2 months ago

  • Fixed in Releases smart_proxy_remote_execution_ssh-0.6.0 added
  • Fixed in Releases deleted (smart_proxy_remote_execution_ssh-0.5.3)

#5 Updated by The Foreman Bot 2 months ago

  • Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/78 added

#6 Updated by Adam Ruzicka about 1 month ago

  • Fixed in Releases smart_proxy_remote_execution_ssh-0.7.0 added
  • Fixed in Releases deleted (smart_proxy_remote_execution_ssh-0.6.0)

Also available in: Atom PDF