[openstack-dev] [keystone][doc][tempest] What title should be for OS-KSCRUD extension

Dolph Mathews dolph.mathews at gmail.com
Wed Dec 9 03:33:21 UTC 2015


I just noticed you suggested "<verb> <subject>"; if that's the prevailing
form, then I'd suggest "Change password (self-service)".

On Tue, Dec 8, 2015 at 9:31 PM, Dolph Mathews <dolph.mathews at gmail.com>
wrote:

> This is implemented as a "self-service user password change" on the v2
> public API. The user is required to have a token for the password they are
> changing, and is required to know the original password before a new one
> can be set.
>
> There is a similar "administrative password reset" call on the v2 admin
> API (contrib.admin_crud) which does not require the original password:
>
>
> https://github.com/openstack/keystone/blob/master/keystone/contrib/admin_crud/core.py#L104-L114
>
> On Tue, Dec 8, 2015 at 8:56 PM, Ken'ichi Ohmichi <ken1ohmichi at gmail.com>
> wrote:
>
>> Hi Keystone-team,
>>
>> TL;DR:
>>   Keystone v2 API supports PATCH on '/OS-KSCRUD/users/{user_id}',
>>   What should we name the operation for?
>>
>> We are adding the api-site link to Tempest docstring for explaining
>> how to use each REST APIs of each project.
>> This work comes from previous discussion on openstack-dev[1].
>> We can find problems on Tempest and the api-site and solve them, that
>> is good thing for improving the quality.
>> During this work[2], we are facing a problem difficult to distinguish
>> what title is the best for OS-KSCRUD extension on Keystone v2 API.
>>
>> Keystone v2 API provides an API on "OS-KSCRUD/users/<user-id>" with PATCH.
>> That seems "Update user" from REST design, but according to the
>> following Keystone implementation, that seems "Set user password".
>>
>> keystone/contrib/user_crud/core.py
>> 131         mapper.connect('/OS-KSCRUD/users/{user_id}',
>> 132                        controller=user_controller,
>> 133                        action='set_user_password',   <HERE>
>> 134                        conditions=dict(method=['PATCH']))
>>
>> Which is the best for this API?
>>
>> The api-site doesn't contain this API description[3], so it will be
>> great to get feedback for improving both the api-site and Tempest.
>>
>> Thanks
>> Ken Ohmichi
>>
>> ---
>> [1]:
>> http://lists.openstack.org/pipermail/openstack-dev/2015-July/068864.html
>> [2]: https://review.openstack.org/#/c/253806/
>> [3]: https://bugs.launchpad.net/openstack-api-site/+bug/1524153
>>
>> __________________________________________________________________________
>> 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-dev/attachments/20151208/c8103a2b/attachment.html>


More information about the OpenStack-dev mailing list