Jason, <div> Sounds like the model you're proposing could be achieved by something like this:</div><div><br></div><div>On Keystone:</div><div>- Roles are identified by name and contain tuples in the form of:</div><div>
-- the service to which this permission applies (e.g. service nova, swift). Including the service is meant to side track attempts to normalize actions across very different types of services</div><div> -- the type of target this action applies to - e.g. volume, network port etc.</div>
<div> -- action this permission allows - e.g. start vm, create volume.</div><div> </div><div>- An authorize API call which accepts: </div><div> - the service requesting the authorization</div><div> - user token (from a previous authentication) </div>
<div> - tenant ID (to resolve the realm of the user token)</div><div> - a target type</div><div> - the attempted action.</div><div><br></div><div> This API would lookup the token, and if its present combine a set of the relevant permissions from all the roles the token is referencing. If the requested tuple exists in this combine set, the request is authorized.</div>
<div><br><div><div><div><div><div><div><div>A few caveats remain:</div><div><br></div><div>a) the above description doesn't include Resource Groups... as Ziad mentioned, that is currently differed. When those are introduced, the service should probably pass the instance-id of the target, and Keystone would have to take that into account.</div>
<div><br></div><div>b) the current API's in keystone allows a service to perform actions on multiple instances across tenants (containers) efficiently - a service could obtain a list of accessible tenants and cache it. If only the 'authorize' API is available, the service would need to perform a check with keystone for every instance </div>
<div><br></div><div>c) In this model it is required to populate role definitions into keystone, for all services. Since keystone should be independent of other services, the set of actions/targets should probably be considered as ""data"" for it - requiring a deployment step of sorts to make keystone aware of these roles.</div>
<div>This could be avoided if the authorization decision is looked at as 2 separate steps:</div><div> 1. figure out what roles a user posses. </div><div> 2. expand the set of roles to set of actions allowed</div><div> 3. determine if the action attempted is allowed</div>
<div><br></div><div>it is obviously debatable where keystone ends and the services begin. In the model above, keystone is responsible for all 3 steps via the authorize API. I *think* the current API provides a very similar model, with the line drawn at 1 - i.e. keystone provides to roles, and there is a separate middleware piece to perform 2 & 3, executing in the request pipleline of the service. Where this middleware executes (i.e. what is the API boundary to keystone) doesn't necessarily change the overall model. </div>
<div><br></div><div>I *think*.</div><div><br></div><div><br></div><div><br></div><div> </div><div><br></div><div><br></div><div><br></div><div><br><br><div class="gmail_quote">On Wed, Jun 15, 2011 at 11:52 AM, Rouault, Jason (Cloud Services) <span dir="ltr"><<a href="mailto:jason.rouault@hp.com" target="_blank">jason.rouault@hp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">In my opinion the services (and their developers) should not need to interpret roles thus resulting in varying semantics. Roles should be defined by a set of configurable privileges to perform certain <u>actions</u> on specific <u>targets</u> for particular <u>services</u>. The API should only need to know to check with an authorization subsystem whether the incoming request is allowed based on the who is making the request and the 3-tuple mentioned previously. </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Jason</span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> andi abes [mailto:<a href="mailto:andi.abes@gmail.com" target="_blank">andi.abes@gmail.com</a>] <br>
<b>Sent:</b> Wednesday, June 15, 2011 9:18 AM<br><b>To:</b> Rouault, Jason (Cloud Services)<br><b>Cc:</b> Ziad Sawalha; <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
<b>Subject:</b> Re: [Openstack] OpenStack Identity: Keystone API Proposal</span></p>
<div><div></div><div><p class="MsoNormal"> </p><p class="MsoNormal">I would expect that the API of each service would have to interpret the role assigned to a user in the context of that service - roles for swift nova glance quantum etc would probably carry very different semantics.</p>
<div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">So, to my understanding, key stone provides authentication and user information - what tenants the user has access to, and what roles the user is assigned. The mapping of these to what the user can do on what instances in each service are left for the service to determine.</p>
</div><div><p class="MsoNormal" style="margin-bottom:12.0pt"> </p><div><p class="MsoNormal">On Wed, Jun 15, 2011 at 10:32 AM, Rouault, Jason (Cloud Services) <<a href="mailto:jason.rouault@hp.com" target="_blank">jason.rouault@hp.com</a>> wrote:</p>
<div><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Is there a plan to also have Keystone be the centralizing framework around authorization? Right now it looks like policy enforcement is left to the API layer.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thanks,<br><br>Jason</span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> openstack-bounces+jason.rouault=<a href="http://hp.com" target="_blank">hp.com</a>@<a href="http://lists.launchpad.net" target="_blank">lists.launchpad.net</a> [mailto:<a href="mailto:openstack-bounces%2Bjason.rouault" target="_blank">openstack-bounces+jason.rouault</a>=<a href="http://hp.com" target="_blank">hp.com</a>@<a href="http://lists.launchpad.net" target="_blank">lists.launchpad.net</a>] <b>On Behalf Of </b>Ziad Sawalha<br>
<b>Sent:</b> Friday, June 10, 2011 5:24 PM<br><b>To:</b> <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br><b>Subject:</b> [Openstack] OpenStack Identity: Keystone API Proposal</span></p>
</div></div><div><div><p class="MsoNormal"> </p><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black">Time flies! It's June 10th already. In my last email to this community I had proposed today as the day to lock down the Keystone API so we can finalize implementation by Diablo-D2 (June 30th).</span></p>
</div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span></p></div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black">We've been working on this feverishly over the past couple of weeks and have just pushed out a proposed API here: <a href="https://github.com/rackspace/keystone/raw/master/keystone/content/identitydevguide.pdf" target="_blank">https://github.com/rackspace/keystone/raw/master/keystone/content/identitydevguide.pdf</a></span></p>
</div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span></p></div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black">For any and all interested, the original source and code is on Github (<a href="https://github.com/rackspace/keystone/raw/master/keystone/content/identitydevguide.pdf" target="_blank">https://github.com/rackspace/keystone</a>), along with the current implementation of Keystone, examples, sample data, tests, instructions, and all the goodies we could muster to put together. The project also lives on Launchpad at <a href="http://launchpad.net/keystone" target="_blank">http://launchpad.net/keystone</a>.</span></p>
</div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span></p></div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black">The API we just put out there is still a proposal. We're going to be focusing on the implementation, but would still love to get community input, feedback, and participation.</span></p>
</div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span></p></div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black">Have a great weekend and regards to all,</span></p></div><div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span></p></div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black">Ziad</span></p></div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span></p>
</div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span></p></div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span></p></div><div><p class="MsoNormal"><span style="font-size:10.5pt;color:black"> </span></p>
</div><pre><span style="color:black"> </span></pre><pre><span style="color:black">Confidentiality Notice: This e-mail message (including any attached or</span></pre><pre><span style="color:black">embedded documents) is intended for the exclusive and confidential use of the</span></pre>
<pre><span style="color:black">individual or entity to which this message is addressed, and unless otherwise</span></pre><pre><span style="color:black">expressly indicated, is confidential and privileged information of Rackspace.</span></pre>
<pre><span style="color:black">Any dissemination, distribution or copying of the enclosed material is prohibited.</span></pre><pre><span style="color:black">If you receive this transmission in error, please notify us immediately by e-mail</span></pre>
<pre><span style="color:black">at <a href="mailto:abuse@rackspace.com" target="_blank">abuse@rackspace.com</a>, and delete the original message.</span></pre><pre><span style="color:black">Your cooperation is appreciated.</span></pre>
</div></div></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a></p></div><p class="MsoNormal"> </p></div></div></div></div></div></blockquote></div><br></div></div></div>
</div></div></div></div>
</div>