<div dir="ltr"><div>Hi Michal,<br><br>Okay.. Thanks..<br><br></div>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 ?<br>
<br></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><span>-- <br></span>Regards
<br>Shanil
</div></div>
<br><br><div class="gmail_quote">On Tue, Jul 8, 2014 at 7:28 PM, Michal Skrivanek <span dir="ltr"><<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
On Jul 8, 2014, at 09:37 , Shanil S <<a href="mailto:xielesshanil@gmail.com">xielesshanil@gmail.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> 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.<br>
><br>
> I am planning to use the console from the browser using the novnc console ( <a href="http://kanaka.github.io/noVNC/" target="_blank">http://kanaka.github.io/noVNC/</a> ) 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 ?<br>
<br>
</div></div>Hi,<br>
you'd have to do it the same way as the backend java code does that.<br>
There's no special shortcut/API.<br>
<br>
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.<br>
<br>
Thanks,<br>
michal<br>
><br>
><br>
<span class="HOEnZb"><font color="#888888">><br>
> --<br>
> Regards<br>
> Shanil<br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br>
</font></span></blockquote></div><br></div>