Project

General

Profile

Feature #544

foreman<->smart-proxy communication should support ssl

Added by Paul Kelly over 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Paul Kelly
Category:
Proxy gateway
Target version:
0.3
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

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

Associated revisions

Revision 455f5d2b (diff)
Added by Paul Kelly about 12 years ago

Fixes #544 - Foreman connects using an ssl certificate

Signed-off-by: Paul Kelly <>

History

#1 Updated by Ohad Levy about 12 years ago

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

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

#2 Updated by Paul Kelly about 12 years ago

  • Status changed from New to Ready For Testing

#3 Updated by Paul Kelly about 12 years ago

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

#4 Updated by Ohad Levy about 12 years ago

  • Target version set to 0.3

#5 Updated by Paul Kelly about 12 years ago

  • % Done changed from 0 to 100

#6 Updated by Ohad Levy about 12 years 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