I don't imagine many scenarios where we would need to do this. The list of authorized tenants should be relatively static, I don't see a strong need to change the list midruntime. What sort of scenario would necessitate that? 

> On Apr 2, 2014, at 11:47 AM, Justin Gallardo <notifications@github.com> wrote:
> 
> In blueflood-http/src/main/java/com/rackspacecloud/blueflood/service/HttpConfig.java:
> 
> > @@ -52,7 +52,11 @@
> >  
> >      // Timeout (in seconds) for batch query. This value depends on number of threads, read latency per
> >      // metric and max metrics allowed per batch query.
> > -    BATCH_QUERY_TIMEOUT("20");  // 20s
> > +    BATCH_QUERY_TIMEOUT("20"),  // 20s
> > +
> > +    // Comma separated list of tenant ids which are allowed to submit data on behalf of other tenants.
> > +    // Useful when auth is handled at a proxy layer before reaching blueflood.
> > +    AUTHORIZED_AGENT_TENANTS("agent");
> That is what I gathered. It seems like we wouldn't want to have to restart blueflood if we want to 'authorize' a new tenant to submit for others. Or am I way off?
> 
> —
> Reply to this email directly or view it on GitHub.