anchor.diff:  
   == console authorisation
   
  +Permissions for enmasse will be assigned to groups (or roles). The
  +groups are defined in the authorisation service.
  +
  +There will be two permissions defined for access to the console:
  +
  +1. read access
  +
  +2. write access (allowing creation and deletion of addresses)
  +
  +The console should use OAuth to verify whether a given user has been
  +granted these permissions.
  +
   == configuring authentication for an address-space
   
   Three options presented to user:
  
positive.code: openshift/kubernetes userbase, presumably using OAuth tokens supplied
  in the HTTP headers.
  
  === service broker/service catalogue
  
  The service broker implementation is part of the address
  controller. This really just represents a slightly different API into
  
negative.code:  }
  ....
  
  Routers will need to specify the the realm for their address-space in
  the AMQP open frames hostname field in connections made to the
  authentication service via sasl-delegation.
  
  If the host is used to identify the realm, we would need a unique
  hostname per address-space, i.e. a route per address-space.
  
  Alternatively, the realm could be specified as a separate option.
  
  The address controller will allow the authentication service to be
  specified, and will set environment variables in the router deployment
  describing the host and port and path to the CA cert to use. The CA
  cert will be mounted as a secret.
  
  == testing
  
  