[ovirt-users] Vm console creation using noVNC

[Shanil S]

Hi Michal,

Okay.. Thanks..

But still i am not sure how can i create the encrypted ticket details. When
i decoded i got validFrom,validTo,data,signature and salt and this is
dynamic and each time we open a console it will be regenerated but i didn't
find out any doc about how we can encode these details. Is there any
special method to encrypt the ticket details for console ?


-- 
Regards
Shanil


On Tue, Jul 8, 2014 at 7:28 PM, Michal Skrivanek <
michal.skrivanek at redhat.com> wrote:

>
> On Jul 8, 2014, at 09:37 , Shanil S <xielesshanil at gmail.com> wrote:
>
> > Hi,
> >
> > I am creating console using api, for this i created a ticket using the
> rest api and used the ticket value as password and i am able to connect it
> using these details using vnc client.
> >
> > I am planning to use the console from the browser using the novnc
> console ( http://kanaka.github.io/noVNC/ ) as like the same way which
> used in the ovirt panel. When i checked the novnc-main.html it is found
> that the ticket information details are passing in the encrypted format and
> passing the signature and salt and ticket details as an array, Could you
> please tell me how can i create these details in the encoded format and
> create a console using noVnc and rest api ?
>
> Hi,
> you'd have to do it the same way as the backend java code does that.
> There's no special shortcut/API.
>
> depending on what are you specifically doing, you may not even need to do
> that. If you bypass ovirt's websocket-proxy and e.g. connect to hosts
> directly (and run/setup websocket proxy "your own way") then you can also
> implement the security of client<->proxy in some other way.
>
> Thanks,
> michal
> >
> >
> >
> > --
> > Regards
> > Shanil
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140709/6e9c1154/attachment-0001.html>