I was just trying to understand how the id information is spreading through
the ovirt communication channels.
I am also interested if the session ids which are sent between client and
ovirt-engine are sent further to vdsm.

пн, 26 нояб. 2018 г. в 17:16, Dan Yasny <[email protected]>:

> Maybe if you could tell us what you are trying to do or achieve, we might
> give you the answers directly
>
> On Mon, Nov 26, 2018 at 3:18 AM Anastasiya Ruzhanskaya <
> [email protected]> wrote:
>
>> Hello everyone!
>>
>> I wanted to find out how the impersonation technique used in oVirt works?
>> I know from libvirt developers, that oVirt opens one connection only for
>> multiple clients. How does this work?
>>
>> Also I found out in source code that in ActionParameterBase class the
>> sessionId field is marked transient but, for example, for GWT rpc message,
>> which goes to the server and says what action will be made (shut down,
>> pause vm) this is the only field in all sent information which says what
>> the session is. Where is the session sent instead? There was also a field
>> with session id in https headers, but this was related to cookie so I am
>> not completely sure if this can help to identify the current user.
>> _______________________________________________
>> Users mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/[email protected]/message/ZPJYRM2XPRPD54E7AWC2V53UZABPJFMY/
>>
>
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/573HH5V5MWBOFNW326NM7MHIVOXRBJN2/

Reply via email to