<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><div>case-insensitive - why would 'Admin' and 'admin' be different? Sure, a role is represented by a string, but why does that string need to be case sensitive?</div><div>I'd think that if you had distinct roles attributed to 'Admin' and 'admin' that that would lead to confusion.<br><br>Cheers,<br><br>Christopher Ferris<br>IBM Distinguished Engineer, CTO Industry and Cloud Standards<br>Member, IBM Academy of Technology<br>IBM Software Group, Standards Strategy<br>email: chrisfer@us.ibm.com<br>Twitter: christo4ferris<br>phone: +1 508 234 2986</div><br><br><font color="#990099">-----openstack-bounces+chrisfer=us.ibm.com@lists.launchpad.net wrote: -----</font><div style="padding-left:5px;"><div style="padding-right:0px;padding-left:5px;border-left:solid black 2px;">To: Kiall Mac Innes <kiall@managedit.ie><br>From: Brian Waldon <brian.waldon@rackspace.com><br>Sent by: openstack-bounces+chrisfer=us.ibm.com@lists.launchpad.net<br>Date: 06/08/2012 07:21PM<br>Cc: "openstack@lists.launchpad.net \(openstack@lists.launchpad.net\)" <openstack@lists.launchpad.net><br>Subject: Re: [Openstack] Comparing roles - case (in)sensitivity<br><br><div>I guess I'm looking at this from more of a purist development point of view: 'Admin' and 'admin' just can't be equal. If I think of this as comparing roles, where a role is an abstract concept, case-insensitivity makes more sense. A string is simply being used to represent the role, where the intent of the role is what really needs to be compared.</div><div><br></div><div>My goal here is to get everybody on board with a single approach and apply it across all projects. I don't *really* care too much which approach we take.</div><div><br></div><div>Waldon</div><br><div><div>On Jun 8, 2012, at 3:27 PM, Kiall Mac Innes wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p>Sure - The most obvious reason is human error leading to a security hole. E.g. Accidently assigning a user "Admin" when you really meant to assign "admin".</p><p>Treating roles as case insensitive helps prevent this kind of human error.</p><p>What advantages does allowing distinct "Admin" and "admin" roles provide?</p><p>Thanks,<br>
Kiall</p><p>Sent from my phone.</p>
<div class="gmail_quote">On Jun 8, 2012 11:20 p.m., "Brian Waldon" <<a href="mailto:brian.waldon@rackspace.com">brian.waldon@rackspace.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Can you explain why?<div><br><div><div>On Jun 8, 2012, at 3:18 PM, Kiall Mac Innes wrote:</div><br><blockquote type="cite"><p>No, I'm suggesting they should all be treated as a single role. I.e. roles should be case insensitive.<br>
</p><p>Thanks,<br>
Kiall</p><p>Sent from my phone.</p>
<div class="gmail_quote">On Jun 8, 2012 11:16 p.m., "Brian Waldon" <<a href="mailto:brian.waldon@rackspace.com" target="_blank">brian.waldon@rackspace.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">I'm suggesting we support only a single representation of a role across all projects: 'admin', 'Admin', and 'admIn' would be three separate roles.<div><br></div>
<div>Are you suggesting otherwise?</div><div><br></div><div><div><div>On Jun 8, 2012, at 3:14 PM, Kiall Mac Innes wrote:</div><br><blockquote type="cite"><p>What's the argument for allowing both, for example, "admin", "Admin" and "admIn" roles?</p><p>This seems like one place where case insensitive makes the most sense.</p><p>Thanks,<br>
Kiall</p><p>Sent from my phone.</p>
<div class="gmail_quote">On Jun 8, 2012 11:01 p.m., "Joseph Suh" <<a href="mailto:jsuh@isi.edu" target="_blank">jsuh@isi.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'd vote case-sensitive.<br>
<br>
Joseph<br>
<br>
----<br>
(w) <a href="tel:703-248-6160" value="+17032486160" target="_blank">703-248-6160</a><br>
(c) <a href="tel:571-340-2434" value="+15713402434" target="_blank">571-340-2434</a><br>
(f) <a href="tel:703-812-3712" value="+17038123712" target="_blank">703-812-3712</a><br>
3811 N. Fairfax Drive Suite 200<br>
Arlington, VA, 22203, USA<br>
<a href="http://www.east.isi.edu/~jsuh" target="_blank">http://www.east.isi.edu/~jsuh</a><br>
<br>
----- Original Message -----<br>
From: "Brian Waldon" <<a href="mailto:brian.waldon@rackspace.com" target="_blank">brian.waldon@rackspace.com</a>><br>
To: "<a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a> (<a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a>)" <<a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a>><br>
Sent: Friday, June 8, 2012 5:50:45 PM<br>
Subject: [Openstack] Comparing roles - case (in)sensitivity<br>
<br>
<br>
<br>
tl;dr - Should we compare roles as case-sensitive or case-insensitive? I vote case-sensitive.<br>
<br>
This bug was recently filed in Glance: <a href="https://bugs.launchpad.net/glance/+bug/1010519" target="_blank">https://bugs.launchpad.net/glance/+bug/1010519</a> . It points out that Nova and Keystone are both case-insensitive when it comes to role comparison, yet Glance *is* case sensitive. I'm in favor of moving other projects to a case-sensitive approach for two main reasons:<br>
<br>
<br>
1) If a role is a string, and comparing strings is inherently case-sensitive, then role comparison would logically be case-sensitive<br>
2) I get to do less work<br>
<br>
<br>
<br>
Thoughts?<br>
<br>
<br>
Brian Waldon<br>
<br>
<br>
<br>
<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>
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>
</blockquote></div>
</blockquote></div><br></div></div></blockquote></div>
</blockquote></div><br></div></div></blockquote></div>
</blockquote></div><br>
<div><font face="Courier New,Courier,monospace" size="3">_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : openstack@lists.launchpad.net<br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></font></div></brian.waldon@rackspace.com></div></div><div></div></font>