Brightbox
  • Home
  • Pricing & Sign up
  • Why Brightbox?
  • Products & Services
  • FAQs
  • About
  • Blog
  • Wiki
  • Contact
Blog RSS feed
twitter_banner

Flickr


more images...

Recent Posts

  • New deployment gem release, better bundler support
  • Passenger 3.0.11 Ubuntu Packages
  • Brightbox Cloud - general availability
  • It's a new brand day!
  • Apache Denial-of-Service Vulnerability

Archives

  • December 2011 (1)
  • November 2011 (1)
  • October 2011 (1)
  • September 2011 (2)
  • August 2011 (2)
  • May 2011 (1)
  • March 2011 (3)
  • January 2011 (1)
  • November 2010 (6)
  • September 2010 (4)
  • August 2010 (1)
  • June 2010 (3)
  • May 2010 (1)
  • April 2010 (3)
  • March 2010 (2)
  • February 2010 (3)
  • January 2010 (6)
  • December 2009 (4)
  • November 2009 (6)
  • October 2009 (2)
  • September 2009 (3)
  • August 2009 (4)
  • July 2009 (3)
  • June 2009 (3)
  • May 2009 (5)
  • April 2009 (4)
  • March 2009 (4)
  • February 2009 (3)
  • January 2009 (6)
  • December 2008 (8)
  • November 2008 (7)
  • October 2008 (8)
  • September 2008 (3)
  • August 2008 (5)
  • July 2008 (1)
  • June 2008 (4)
  • May 2008 (4)
  • April 2008 (3)
  • March 2008 (3)
  • February 2008 (3)
  • January 2008 (4)
  • December 2007 (4)
  • November 2007 (3)
  • October 2007 (1)
  • August 2007 (7)
  • July 2007 (1)
  • June 2007 (3)

Popular tags

    • announcements
    • apache
    • beta
    • deployment
    • hardy
    • packages
    • passenger
    • performance
    • phusion
    • rack
    • rails
    • ruby
    • ruby on rails
    • security
    • ubuntu

Tag Cloud

announcements apache beta brightbox brightbox cloud brightbox gem cloud conference control panel dapper debian deployment events gem hardy hosting launch leeds linux london lucid maintenance modrails mod_rails mysql network nginx packages passenger performance phusion pricing rack rails rails hosting ruby ruby on rails security team tech ubuntu uk updates upgrade xen

Posts tagged ‘login’

New: Automatically add SSH keys to new Brightboxes 3 Jun 10

Getting access to your newly purchased Brightboxes used to require a trip to the control panel to retrieve the ‘rails’ user password. If you’re using config management systems like Chef or Puppet this is likely the only laborious aspects of configuring your box. No longer!

Now, whenever a new box is deployed, the SSH keys of all the technical contacts on your Brightbox account are automatically pre-installed for the default ‘rails’ user. To add your own SSH key, edit your user profile within the control panel and paste in your SSH public key using the editor at the bottom.

Remember, this only affects newly provisioned boxes – as the it’s done during the box build stage. Removing or adding technical contacts in the control panel at a later date will not automatically change any access control on existing boxes.

Posted 3 June 2010 by John Leach • Comments Off

access+ authentication+ brightbox+ deployment+ keys+ login+ security+ ssh

Important announcement: Multiple users and accounts release 11 Feb 10

We recently previewed some upcoming changes to how users interact with Brightbox accounts. This feature will be going live at 12:00 GMT on Weds 17 Feb and since it represents a change in behaviour for existing customers, I’ve summarised the details below.

Maintenance period

Starting at 12:00 (midday) on Weds 17 Feb, the Brightbox control panel will be unavailable for approximately 20 minutes whilst we perform the updates. One of the updates will include a migration to create an owner user account (name and email address) for all existing active customer accounts.

Change of login from “username” to email address

Once the above maintenance period is completed, you’ll be able to login to the control panel again as normal, but now using your registered email address to login, together with the existing password.

Adding and inviting users

Once logged in you’ll be able to give other people access to your account via the “User access” link.

It’s important to note that initially, as described below, all users that you give access to your account will have full access (apart from the ability to invite other users).

Interim billing and technical roles

Currently, customers are able to specify two additional “contacts” on their account – a billing contact (receives cc’ed payment email notifications) and a technical contact (receives copies of support ticket notifications and server notifications). These “old style” contacts do not have access to the account, unless the account owner supplies them with the account username and password.

The main purpose of this work is to enable a “many to many” relationship between users and accounts i.e multiple users can access a single account and single users can have multiple accounts. We will be introducing a more extensive permissions system into the control panel in due course, but in the meantime the four “roles” that users can have will each have full access to the account but differ in their behaviour…

  • Owner (one per account): Full access + add/invite new users to have access. The owner role is the person ultimately responsible for the account and can’t be assigned by users.
  • Primary technical (one per account): Full access + single point of contact for Brightbox technical support to receive email notifications etc
  • Technical (many per account): Full access.
  • Billing (many per account): Full access + receive copies of payment email notifications

If you have any questions about these changes and how they will affect you, please drop us an email.

Posted 11 February 2010 by Jeremy Jarvis • Comments Off

accounts+ announcements+ login+ users

Preview: Multiple users and accounts 15 Jan 10

Right now, each Brightbox customer has a single username/password to access their Brightbox account. For many smaller customers, this works fine and they can easily operate the various aspects of their account themselves e.g manage virtual machines, billing and support tickets. However, there are also a number of scenarios where this doesn’t work too well – especially when there are multiple people managing one or more accounts.

We’ve been developing a more robust solution for users and accounts for some time and hope to launch this new system in the next few weeks. In this post, I’d like to give a sneak preview on the forthcoming changes…

  • Each person will have a Brightbox user account
  • We’ll be introducing a number of “roles” (tbc)
  • Each account will always have an “owner” contact, this person is ultimately responsible for the account
  • Existing Brightbox account holders will be migrated to a new owner contact
  • The account owner will be able to invite additional users to their account
  • The control panel will enable users with access to multiple accounts to easily move between the accounts to which they have access

Over the next couple of weeks, all customers will receive an email explaining the changes and the migration process.

Posted 15 January 2010 by Jeremy Jarvis • 5 comments

accounts+ login+ security+ users


Recent blog posts

  • New deployment gem release, better bundler support
    2 months ago
  • Passenger 3.0.11 Ubuntu Packages
    2 months ago
  • Brightbox Cloud – general availability
    4 months ago
  • It’s a new brand day!
    4 months ago
  • Apache Denial-of-Service Vulnerability
    5 months ago
  • Pricing for Brightbox Cloud (and last call for private beta)
    5 months ago

Join our email list

Flickr (more...)

RSS feeds

Blog feed

Flickr feed

Recent Wiki updates

System Status feed




Wiki | Forums | Terms & Conditions | Privacy | Site Map

Copyright © 2011 Brightbox Systems Ltd. All rights reserved