Project

General

Profile

Actions
Copy link

Bug #15442

closed

Make the dynflow core working with client certs

Added by Ivan Necas almost 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ivan Necas
Category:
Smart Proxy Dynflow
Target version:
smart_proxy_dynflow 0.1.3
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/smart_proxy_dynflow/pull/21
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Right now, we counted on the fact that the client certs and https certs will be the same,
which is not true always (not when using custom certs). We should have different options
for https certs and client certs, as the foreman proxy has

Actions
Copy link
 #1

Updated by The Foreman Bot almost 8 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/smart_proxy_dynflow/pull/21 added
Actions
Copy link
 #2

Updated by Marek Hulán almost 8 years ago

  • Target version set to 99
Actions
Copy link
 #3

Updated by Marek Hulán almost 8 years ago

  • translation missing: en.field_release set to 167
Actions
Copy link
 #4

Updated by Ivan Necas almost 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF