Open Stack

forwarding to the Operators list too.

The keystone team is wondering if folks are using the OS-OAUTH1 extension
in the wild. If not we would like to deprecate it.

The extension allows users to delegate roles on a project (very similar to
Trusts), but the flow of creating this relationship is done with OAuth
APIs. The spec can be found here:
http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3-os-oauth1-ext.html

Thanks,

Steve Martinelli
OpenStack Keystone Project Team Lead
----- Forwarded by Steve Martinelli/Toronto/IBM on 2016/03/17 06:53 AM
-----

From:	Alexander Makarov <amakarov at mirantis.com>
To:	"OpenStack Development Mailing List (not for usage questions)"
            <openstack-dev at lists.openstack.org>
Date:	2016/03/17 06:04 AM
Subject:	[openstack-dev] [keystone] Does anybody need OAuth1 API in
            keystone?



Hi!

I'm working on unifying all the models that store actor access rights to
the resources [0],
and now I'm wondering if we can just drop current OAuth1 implementation
[1].
It's definitely not perfect and require considerable effort to bring it in
good shape so the question is if the feature worth the attention?

​[0]​ https://blueprints.launchpad.net/keystone/+spec/unified-delegation
[1] https://github.com/openstack/keystone/tree/master/keystone/oauth1

--
Kind Regards,
Alexander Makarov,
Senior Software Developer,

Mirantis, Inc.
35b/3, Vorontsovskaya St., 109147, Moscow, Russia

Tel.: +7 (495) 640-49-04
Tel.: +7 (926) 204-50-60

Skype: MAKAPOB.AJIEKCAHDP
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160317/6ef5c6b2/attachment.html>