Feature #544

foreman<->smart-proxy communication should support ssl

Added by Paul Kelly over 1 year ago. Updated about 1 year ago.

Status:Closed Start:12/16/2010
Priority:Normal Due date:
Assigned to:Paul Kelly % Done:

100%
Category:Proxy gateway
Target version:0.3
Backlog:No Difficulity:
Votes: 0

Description

A https connection should be the default for smart-proxy requests

Associated revisions

Revision 455f5d2ba487abc6fc7d52c8ce164f0a0834bc2e
Added by Paul Kelly about 1 year ago

Fixes #544 - Foreman connects using an ssl certificate

Signed-off-by: Paul Kelly <>

History

Updated by Ohad Levy about 1 year ago

  • Category set to Proxy gateway
  • Assigned to set to Paul Kelly

Paul, do you want to include this one in 0.2?

Updated by Paul Kelly about 1 year ago

  • Status changed from New to Ready For Testing

Updated by Paul Kelly about 1 year ago

Only connects using ssl if the smartproxy url is https://XXXX

Updated by Ohad Levy about 1 year ago

  • Target version set to 0.3

Updated by Paul Kelly about 1 year ago

  • % Done changed from 0 to 100

Updated by Ohad Levy about 1 year ago

  • Status changed from Ready For Testing to Closed

it already supported ssl, this patch adds SSL verifications based on certificates (allowing to reuse puppet certificates as well).

Paul, would you mind documenting this change somewhere?

Also available in: Atom PDF