<div dir="ltr"><div>Yes, we will take a SSO token using SSO auth Rest API call and use the same token for all the API hits for next 4 days (Example If 4 days is the SSO token timeout). Is there an issue with using like that?<br><br></div>If there is a session concept there for SSO token in using as Rest API?<br><br> <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 8, 2018 at 11:05 PM, Hari Prasanth Loganathan <span dir="ltr"><<a href="mailto:hariprasanth.l@msystechnologies.com" target="_blank">hariprasanth.l@msystechnologies.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Hi Yaniv,<br><br></div>To give an example, We are planning to create and manage our VM's using oVirt. <br></div>Instead of managing oVirt using UI, We will be writing the script which hits the oVirt engine periodically for different functionality. so We would like to take a benchmark to finalise the number of hits to ovirt.<br><br></div>This is what we are trying to achieve.<br><br></div>Coming to my query,<br></div><div>What is the difference between sso token and session maintance in oVirt, If I have a token timeout of 4 days, How the concept of session plays a role in oVirt?<br><br></div><div>Thanks,<br></div><div>Hari <br></div><div><div><br></div></div></div>
</blockquote></div><br></div>
<br>
<p style="text-align:justify"><span lang="EN-US"><font size="1">DISCLAIMER</font></span></p>
<p style="text-align:justify"><font size="1"><span lang="EN-US">The information in this e-mail is confidential and may be subject to
legal privilege. It is intended solely for the addressee. Access to this e-mail
by anyone else is unauthorized. If you have received this communication in
error, please address with the subject heading "Received in error,"
send to <a href="mailto:it@msystechnologies.com" target="_blank">it@msystechnologies.com</a>,
then delete the e-mail and destroy any copies of it. If you are not the
intended recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be unlawful.
The views, opinions, conclusions and other information expressed in this
electronic mail and any attachments are not given or endorsed by the company
unless otherwise indicated by an authorized representative independent of this
message.</span></font></p>
<font size="1"><span lang="EN-US">MSys cannot guarantee
that e-mail communications are secure or error-free, as information could be
intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or
contain viruses, though </span>all reasonable
precautions have been taken to ensure no viruses are present in this e-mail<span lang="EN-US">. </span>As our company cannot accept responsibility for
any loss or damage arising from the use of this e-mail or attachments we
recommend that you subject these to your virus checking procedures prior to use</font>