44 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• John Larsen commented  ·  May 14, 2012 12:23  ·  Flag as inappropriate  ·  Delete

  Agreed. The Cloud Hosting Control Panel needs to allow for multiple administrators with varying levels of account access. Some sort of ACL is absolutely required from a compliance perspective. I would add there should also be logging of activity so one can see who is doing what from within the control panel.

• Jim Edelstein commented  ·  May 04, 2012 14:38  ·  Flag as inappropriate  ·  Delete

  This is a serious problem for us, please address ASAP - multiple API users doesn't really cut it

• John Oltman commented  ·  April 30, 2012 12:27  ·  Flag as inappropriate  ·  Delete

  This is an important feature for me as well. Need the ability for a role that can see servers, submit tickets via the portal etc but cannot wipe out my account either by accident or maliciously.

• Kyle Heironimus commented  ·  April 12, 2012 07:12  ·  Flag as inappropriate  ·  Delete

  As of April 12, 2012, I have successfully added additional users to the API and can use them in the API, but they are not usable in the portal. It's a start, at least.

  As a user migrating from Slicehost, this is a big step back.

• acgann commented  ·  March 30, 2012 14:41  ·  Flag as inappropriate  ·  Delete

  Sure it does. http://docs.rackspace.com/auth/api/v2.0/auth-client-devguide/content/POST_addUser__.html#webhelp-currentid

  You can add multiple users via the API. The implementation could go further, but at least it's a start. One thing I want to see is if once these users are created via the API if you can use them on the Rackspace App for example or the my.rackspace portal. So you keep the master user and API key separate and give your devs access to your machines with the API keys. Still gives too much access but if someone leaves, at least you have a way to revoke them immediately without killing all your other stuff. Also, I would set a separate user/pw for scripts lighting off backups or using cloud files. Need to kick the tires on this to see what all we can actuall do.

• dtb71 commented  ·  March 30, 2012 14:35  ·  Flag as inappropriate  ·  Delete

  Yeah, I've got same response as @Cory. Glad someone's looking at this.... but couldn't find any reference to multiple users in that page in the API guide -- not sure if that's the wrong link, or what

• Cory commented  ·  March 30, 2012 14:15  ·  Flag as inappropriate  ·  Delete

  This QuickStart document describes how to use a u/p with an API request but makes no reference to multiple users, so I don't see what this has to do with the "multiple control panel users" request. Glad you are working on it, though..?

• Anonymous commented  ·  March 30, 2012 13:19  ·  Flag as inappropriate  ·  Delete

  too little too late, we went elsewhere. One day when you grow up you will have a unified release cycle that allows global clients to use the same features.

• Searchie commented  ·  March 21, 2012 03:34  ·  Flag as inappropriate  ·  Delete

  That was also my first concern after login, happy to read it will come soon. Better sooner then later.

• Aaron Ward commented  ·  February 09, 2012 18:13  ·  Flag as inappropriate  ·  Delete

  This feature is crucial for my business. I would like to duplicate the functionality of my FTP - Allow user to upload and download files from a designated directory.

• Henri Cook commented  ·  February 08, 2012 03:14  ·  Flag as inappropriate  ·  Delete

  I'd also very much enjoy a 'server maintenance' role that could only stop/restart instances and not destroy them completely - that sounds like a recipe for a support-engineer style disaster where instead of rebooting they erase the machine completely and try to recreate it

• Henri Cook commented  ·  February 08, 2012 03:14  ·  Flag as inappropriate  ·  Delete

  Now that we're starting to use Rackspace it's exactly what we need, I don't want to give someone who's working on Cloud Files life-or-death access to all of our server instances as well

• Anonymous commented  ·  February 06, 2012 10:59  ·  Flag as inappropriate  ·  Delete

  well using curl in linux allowed us to get around that. the Json output from that still needs some work. It isn't that hard. 'AWK'ward a perl in the rough, and yeah most people pay peanuts for $helling. However totally doable from the API with curl and 20 minutes. T o upgrade it to RBACS was just a matter of having a tarball prepared from the NSA's released version of linux that they still further tweak, it is a darned good start the url is quite findable.

• Anonymous commented  ·  January 18, 2012 17:08  ·  Flag as inappropriate  ·  Delete

  I need role based access, it would be nice to be granular, in the API as well. Curl, python are my friends.

• Johni Fisher commented  ·  January 18, 2012 16:55  ·  Flag as inappropriate  ·  Delete

  Its a must for us

• arobb commented  ·  January 14, 2012 09:18  ·  Flag as inappropriate  ·  Delete

  They've had multi user on my.rackspace.com for years so it's clearly do-able. It's really shoddy on managed cloud, clearly sharing credentials is a farce.

• Jarl Friis commented  ·  October 12, 2011 11:41  ·  Flag as inappropriate  ·  Delete

  I suggest a solution where one user (the one that enters the payment and invoice details) can delegate technical access such as the server console (the java applet) to a different user.

• Arti Villa commented  ·  October 03, 2011 02:09  ·  Flag as inappropriate  ·  Delete

  Yup! Giving away your username/pass to oversees company is daunting. 3 votes from me :) come on RackSpace!!! The world knows you guys. You can't let your customers down.

• acgann commented  ·  September 29, 2011 07:45  ·  Flag as inappropriate  ·  Delete

  This request is actually over 2 years old. Before the feedback forum, there was a discussion forum that had this thread on it. I know we personally have been asking for this feature for a year and a half.

  This is a complex change as it touches a lot of stuff...the API on the backend, the control panel on the front. And from the roadmap I saw on OpenStack, there are a broad range of improvements (more than just adding more users....more API keys, etc). So I get that developing that isn't an overnight thing. Just *really* tired of waiting.....

  My guess would be 3-9months. I think they're rolling out a new control panel right around the end of the year (if the target hits on time). So we might get it then. Or they may wait until they roll out Nova (CloudServers), in which case probably summer-fall of next year. Of course, I don't work for Rackspace, so this *is* really a guess based on what I currently know (which isn't much).

• Anonymous commented  ·  September 29, 2011 07:26  ·  Flag as inappropriate  ·  Delete

  Another three votes from me - It is Essential... we have this on our Non-cloud services so why not here?