<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Hi PWG,</div><div><br></div><div>Please see the request from Lance below... there is already good discussion going on about this topic on the Dev mailing list in case you want additional context. The main request for us is to determine whether any of our organizations would be willing to help with the implementation of this functionality which improves the AppDev experience by allowing a mechanism to grant access to cloud resources programmatically without the need to create a user account (which shifts the act of authorization from the developer to the administrator). Are any of your teams able to help with implementation? Monty has volunteered to partner with whoever to move the spec forward but won't be able to code it himself.</div><div><br></div><div>Thanks,</div><div>Shamail <br><br><br>Begin forwarded message:<br><br></div><blockquote type="cite"><div><b>From:</b> Lance Bragstad <<a href="mailto:lbragstad@gmail.com">lbragstad@gmail.com</a>><br><b>Date:</b> May 11, 2017 at 3:32:30 PM EDT<br><b>To:</b> "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>, <a href="mailto:user-committee@lists.openstack.org">user-committee@lists.openstack.org</a><br><b>Subject:</b> <b>[openstack-dev] [all][keystone][product] api keys/application specific passwords</b><br><b>Reply-To:</b> "OpenStack Development Mailing List \(not for usage questions\)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br><br></div></blockquote><blockquote type="cite"><div><div dir="ltr"><div>Hey all,</div><div><br></div><div>One of the Baremetal/VM sessions at the summit focused on what we need to do to make OpenStack more consumable for application developers [0]. As a group we recognized the need for application specific passwords or API keys and nearly everyone (above 85% is my best guess) in the session thought it was an important thing to pursue. The API key/application-specific password specification is up for review [1].</div><div><br></div><div>The problem is that with all the recent churn in the keystone project, we don't really have the capacity to commit to this for the cycle. As a project, we're still working through what we've committed to for Pike before the OSIC fallout. It was suggested that we reach out to the PWG to see if this is something we can get some help on from a keystone development perspective. Let's use this thread to see if there is anyway we can better enable the community through API keys/application-specific passwords by seeing if anyone can contribute resources to this effort.</div><div><br></div><div>Thanks,</div><div><br></div><div>Lance</div><div><br></div><div><br></div>[0] <a href="https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal" target="_blank">https://etherpad.<wbr>openstack.org/p/BOS-forum-<wbr>using-vm-and-baremetal</a><div>[1] <a href="https://review.openstack.org/#/c/450415/" target="_blank">https://review.openstack.<wbr>org/#/c/450415/</a></div><div><br></div></div>
</div></blockquote><blockquote type="cite"><div><span>__________________________________________________________________________</span><br><span>OpenStack Development Mailing List (not for usage questions)</span><br><span>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br></div></blockquote></body></html>