Description Szymon Brandys 2011-02-03 11:48:58 EST

Orion already uses delegated identities i.e. OpenIDs. We had a discussion that the user's configuration could be handled in a similar decentralized manner. 

A simple case is:
We have a capability like JS formatter in the editor. Let's say that whether it is enabled or not is part of some user configuration. Also JS formatter preferences are in this configuration. So far the configuration is attached to an Orion instance, so if we have content on many sites e.g. eclipse.org, github.com we need to set the configuration per each host.

I think we could have a service instead to keep the configuration. The configuration could be *injected* into an Orion instance like it is done with authentication via OpenID provider. 

One of approaches is to have OpenID provider with an extension. The configuration would be attached to the identity (OpenID). However I can imagine a scenario when authentication and configuration are served by separate servers.