Bug 1216004 - It isn't possible to disable VM SSO
Summary: It isn't possible to disable VM SSO
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine-cli
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Juan Hernández
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-28 10:49 UTC by Juan Hernández
Modified: 2022-06-30 13:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 10:17:55 UTC
oVirt Team: Infra
Embargoed:
sbonazzo: ovirt-4.1-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46859 0 None None None 2022-06-30 13:06:39 UTC

Description Juan Hernández 2015-04-28 10:49:50 UTC
Currently the RESTAPI supports disabling SSO for a VM sending an empty list of SSO methods:

---8<---
#!/bin/sh -ex

url="https://engine.example.com/ovirt-engine/api"
user="admin@internal"
password="******"

curl \
--insecure \
--user "${user}:${password}" \
--request PUT \
--header "Content-Type: application/xml" \
--header "Accept: application/xml" \
--data '
<vm>
  <sso>
    <methods/>
  </sso>
</vm>
' \
"${url}/vms/7db0f6c8-7328-4cd3-ac06-1ac875511bb3"
--->8---

But this isn't possible with the CLI, as using an empty value for the "--sso-methods-method" option produces an error:

---8<---
[oVirt shell (connected)]# update vm myvm --sso-methods-method ""
============================ ERROR =========================
invalid syntax at "--sso-methods-method", see help on
collection based arguments for more details.
============================================================
--->8---

This happens for any element that allows an empty list of values, not just for SSO methods.

In these cases, when given an empty value, the CLI should send an empty list.

Comment 3 Juan Hernández 2016-05-10 10:17:55 UTC
There aren't plans to update the CLI, so this won't be fixed.


Note You need to log in before you can comment on or make changes to this bug.