<html><body>
<p><font size="2" face="sans-serif">Hi Georgy, </font><br>
<br>
<font size="2" face="sans-serif">The following might help with some of the trust questions you have, if you haven't looked at it already:</font><br>
<a href="https://github.com/openstack/identity-api/blob/master/openstack-identity-api/v3/src/markdown/identity-api-v3-os-trust-ext.md"><font size="3" color="#0000FF" face="serif"><u>https://github.com/openstack/identity-api/blob/master/openstack-identity-api/v3/src/markdown/identity-api-v3-os-trust-ext.md</u></font></a><font size="3" face="serif"> </font><br>
<br>
<font size="2" face="sans-serif">As far as storage implementation, trust uses sql and kvs backends. Trusts can be given an expiration but if an expiration is not given the trust is valid until it is explicitly revoked (taken from the link above): </font><br>
<br>
<font size="2" color="#333333" face="Arial"> Optionally, the trust may only be valid for a specified time period, as defined by </font><font size="1" color="#333333" face="Consolas">expires_at</font><font size="2" color="#333333" face="Arial">. If no</font><font size="1" color="#333333" face="Consolas">expires_at</font><font size="2" color="#333333" face="Arial"> is specified, then the trust is valid until it is explicitly revoked.</font><font size="3" face="serif"> </font><font size="2" face="sans-serif"><br>
</font><br>
<font size="2" face="sans-serif">Trusts can also be given 'uses' so that you can set a limit to how many times a trust will issue a token to the trustee. That functionality hasn't landed yet but it is up for review: </font><a href="https://review.openstack.org/#/c/56243/"><font size="3" color="#0000FF" face="serif"><u>https://review.openstack.org/#/c/56243/</u></font></a><font size="3" face="serif"> </font><br>
<br>
<font size="2" face="sans-serif">Hope this helps! </font><br>
<br>
<font size="2" face="sans-serif"><br>
Best Regards, <br>
<br>
Lance Bragstad <br>
</font><br>
<br>
<img width="16" height="16" src="cid:1__=08BBF6F0DFF718F58f9e8a93df938@us.ibm.com" border="0" alt="Inactive hide details for Georgy Okrokvertskhov ---01/17/2014 12:11:46 PM---Hi, In Solum project we want to use Keystone trusts"><font size="2" color="#424282" face="sans-serif">Georgy Okrokvertskhov ---01/17/2014 12:11:46 PM---Hi, In Solum project we want to use Keystone trusts to work with other</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Georgy Okrokvertskhov <gokrokvertskhov@mirantis.com></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">OpenStack Development Mailing List <openstack-dev@lists.openstack.org>, </font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">01/17/2014 12:11 PM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[openstack-dev] [Solum][Keystone] Best practices for storing keystone trusts information</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<font size="3" face="serif">Hi,</font><br>
<br>
<font size="3" face="serif">In Solum project we want to use Keystone trusts to work with other OpenStack services on behalf of user. Trusts are long term entities and a service should keep them for a long time. </font><br>
<br>
<font size="3" face="serif">I want to understand what are best practices for working with trusts and storing them in a service?</font><br>
<br>
<font size="3" face="serif">What are the options to keep trust? I see obvious approaches like keep them in a service DB or keep them in memory. Are there any other approaches?</font><br>
<br>
<font size="3" face="serif">Is there a proper way to renew trust? For example if I have a long term task which is waiting for external event, how to keep trust fresh for a long and unpredicted period?</font><br>
<br>
<font size="3" face="serif">Thanks</font><br>
<font size="3" face="serif">Georgy</font><tt><font size="2">_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><tt><font size="2"><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font size="2"><br>
</font></tt><br>
</body></html>