Project

General

Profile

Actions
Copy link

Feature #544

closed

foreman<->smart-proxy communication should support ssl

Added by Paul Kelly almost 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Paul Kelly
Category:
Proxy gateway
Target version:
0.3
Difficulty:
Triaged:
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

Actions
Copy link
 #1

Updated by Ohad Levy over 13 years ago

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

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

Actions
Copy link
 #2

Updated by Paul Kelly over 13 years ago

  • Status changed from New to Ready For Testing
Actions
Copy link
 #3

Updated by Paul Kelly over 13 years ago

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

Actions
Copy link
 #4

Updated by Ohad Levy over 13 years ago

  • Target version set to 0.3
Actions
Copy link
 #5

Updated by Paul Kelly over 13 years ago

  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by Ohad Levy over 13 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?

Actions
Copy link

Also available in: Atom PDF