OK, you need to be logged in as an admin to add a ServiceBroker - the question is why is this needed? Can adding a new broker break something that affects other services or ???
Here's the scenario. We have an application that provides a logical service for other apps (in this case a content mgmt service). That app uses some other services for its actual data storage - so it properly runs stateless as an application. Now, I need a service broker (either as part of the app or separate). Then a number of content mgmt solution applications can be built against this new service...
So, why would that require me to be an admin for CF? That prevents someone who isnt the admin of a system from even trying out scenarios like this. Yes, someone could build a proxy/connector (sort of like what AppDirect does for PWS), but ???
Seems like a similar scenario could occur when creating a broker for an external service/database system that is already out there (especially in an enterprise setting) - a connection to Oracle or SAP or ... Again, why would you need a CF administrator to allow usage of these external services?
Yes, you could post a URL somewhere and hand-craft code to connect to it - but everything else in CF is built around the notion of apps binding to services (through service brokers and catalogs).
So, I suspect that there is a very good reason to require admin permission, but it isnt obvious to me what it is - and I cant really find an explanation out there for the reason...
Thanks in advance for an explanation and why it would matter in these use cases.
- Gary