Hi Ollie,

I was able to get the proxy ticket with curl like this:

# curl -k -X POST \

-H "Authorization: Basic YWRLKDFLKnfLfdNLDKDFnsldssL2" \

-H "Accept: application/xml" \

-H "Content-Type: application/xml" \

-d "<action><proxy_ticket><value>ticket_content</value></proxy_ticket></action>" \

-L https://{engine}:443/ovirt-engine/api/vms/{vm:id}/graphicsconsoles/{graphicsconsole:id}/proxyticket

On Thu, Mar 24, 2016 at 4:44 PM, Ollie Armstrong <ollie@fubra.com> wrote:

Hi all,

I'm attempting to use the REST API to get a proxy ticket as BZ1181030
[0] has added support for, but I am unable to find _any_ documentation
on how to use this new API call.

All I've found is the git commit message in gerrit [1].  Not quite
understanding how to interpret this, I've attempted to POST the
following:

<action/>

As well as:

<action> <proxy_ticket> <value>ticket_content</value> </proxy_ticket> </action>

Both of these, and indeed using any other data I can think of, results
in an NPE being logged in engine.log.  I've uploaded my engine.log [2]
which is produced when I POST "<action/>" to the endpoint.

Is anyone able to tell me how to use this endpoint?  I'm assuming I
get the NPE because I'm not POSTing the correct data.  The overall
goal of this is to be able to embed a NoVNC console in our own web UI,
this is the last piece of the puzzle for me to implement this.

Thanks,
Ollie

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1181030
[1] https://gerrit.ovirt.org/#/c/42412/
[2] http://ix.io/uVP
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users