<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Even if we remove this restriction you still need to fetch and examine disabled users only by fetching every user with a get_users call. Do you think whether we need a shorthand
operation just to get the disabled users.I am fine with removing these checks.<br>
<div>
<div style="font-family: Tahoma; font-size: 13px;">
<div class="BodyFragment"><font size="2">
<div class="PlainText">Yogeshwar Srikrishnan<br>
Rackspace</div>
</font></div>
</div>
</div>
<div style="font-family: Times New Roman; color: rgb(0, 0, 0); font-size: 16px;">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF796708"><font color="#000000" face="Tahoma" size="2"><b>From:</b> Mark Gius [mark@markgius.com]<br>
<b>Sent:</b> Wednesday, July 20, 2011 4:12 PM<br>
<b>To:</b> Yogi Srikrishnan<br>
<b>Cc:</b> Jay Pipes; openstack@lists.launchpad.net<br>
<b>Subject:</b> Re: [Openstack] [Keystone] Question from mgius on IRC about update_user API call<br>
</font><br>
</div>
<div></div>
<div>Would you be opposed to removing the check for disabled in get_user, and possibly update_user as well? As it stands now, you can only fetch and examine disabled users by fetching every user with get_users.
<div><br>
</div>
<div>Is there some reason that a disabled user should not be fetched or updated?
<div><br>
</div>
<div>Mark<br>
<div><br>
<div class="gmail_quote">On Wed, Jul 20, 2011 at 1:01 PM, Yogi Srikrishnan <span dir="ltr">
<<a href="mailto:yogesh.srikrishnan@rackspace.com" target="_blank">yogesh.srikrishnan@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Right now the code to update doesn't allow the operation if the user is disabled as there is a separate call to enable/disable user ie /users/userId/enabled .That call should allow the enabling/disabling of user independent of his current status.<br>
Regards<br>
Yogeshwar Srikrishnan<br>
Rackspace<br>
<br>
________________________________________<br>
From: openstack-bounces+yogesh.srikrishnan=<a href="http://rackspace.com" target="_blank">rackspace.com</a>@<a href="http://lists.launchpad.net" target="_blank">lists.launchpad.net</a> [openstack-bounces+yogesh.srikrishnan=<a href="http://rackspace.com" target="_blank">rackspace.com</a>@<a href="http://lists.launchpad.net" target="_blank">lists.launchpad.net</a>]
on behalf of Jay Pipes [<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>]<br>
Sent: Wednesday, July 20, 2011 1:54 PM<br>
To: <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Subject: [Openstack] [Keystone] Question from mgius on IRC about update_user API call<br>
<div>
<div></div>
<div class="h5"><br>
Keystone devs,<br>
<br>
mgius had a question on IRC:<br>
<br>
<mgius> I have a question about Keystone<br>
<mgius> I'm looking to add support to the dashboard so that users can<br>
be enabled or disabled from the dashboard<br>
<mgius> but it looks like in update_user if the target user is<br>
disabled a 403 is always thrown<br>
<mgius> was that intentional?<br>
<br>
-jay<br>
<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><br>
<br>
<br>
</div>
</div>
Confidentiality Notice: This e-mail message (including any attached or<br>
embedded documents) is intended for the exclusive and confidential use of the<br>
individual or entity to which this message is addressed, and unless otherwise<br>
expressly indicated, is confidential and privileged information of Rackspace.<br>
Any dissemination, distribution or copying of the enclosed material is prohibited.<br>
If you receive this transmission in error, please notify us immediately by e-mail<br>
at <a href="mailto:abuse@rackspace.com" target="_blank">abuse@rackspace.com</a>, and delete the original message.<br>
Your cooperation is appreciated.<br>
<div>
<div></div>
<div class="h5"><br>
<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><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
<PRE>
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@rackspace.com, and delete the original message.
Your cooperation is appreciated.
</PRE></body>
</html>