Project

General

Profile

Actions
Copy link

Bug #24391

closed

CA cert can't be specified in API while adding a RHEV Compute Resource

Added by Ido Kanner over 6 years ago. Updated over 5 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
Ido Kanner
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
1602835
Pull request:
https://github.com/theforeman/foreman/pull/5877
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Description of problem:
In WebUI, it is possible (sometimes necessary) to specify a CA certificate for https communication with RHEV. This is done using the "X509 Certification Authorities" field in the new Compute Resource creation form.

In API, this is not possible. Consequently, it is also not possible in Hammer, Nailgun and other tools using API.

Steps to Reproduce:
http://SAT_HOSTNAME/apidoc/v2/compute_resources/create.html

Actual results:
No parameter for CA cert

Expected results:
public_key (id of the WebUI input field) parameter

Related issues 1 (0 open — 1 closed)

Is duplicate of Foreman - Bug #25491: CA cert can't be specified in API while adding a RHEV Compute ResourceClosedShira MaximovActions
Actions
Copy link
 #1

Updated by The Foreman Bot over 6 years ago

  • Pull request https://github.com/theforeman/foreman/pull/5877 added
Actions
Copy link
 #2

Updated by The Foreman Bot over 6 years ago

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

Updated by Anonymous over 5 years ago

  • Is duplicate of Bug #25491: CA cert can't be specified in API while adding a RHEV Compute Resource added
Actions
Copy link
 #4

Updated by Anonymous over 5 years ago

  • Status changed from Ready For Testing to Duplicate
Actions
Copy link

Also available in: Atom PDF