We want to explore the possibility of creating different organizations within our paid apigee account that more closely mirror our business.
At the current time, we have a structure like:
Production Organization: <OurBusiness>
Test Env Organization: <OurBusiness-nonprod>
Due to the fact that our proxies in the original organization seem to be growing at a exponential rate, and we are granting more and more people access to our Organization for development/deployment who really only need access to a small subset of the proxies there, would it be possible to add additional organizations to the original above as our independent Departments start asking for their own proxy development i.e.:
Production Organization: <OurBusiness-groupName(1)>
Test Env Organization: <OurBusiness-groupName(1)-nonprod>
...
Production Organization: <OurBusiness-groupName(N)>
Test Env Organization: <OurBusiness-groupName(N)-nonprod>
Where "groupName(.) would be an actual name (i.e. accounting, security, etc - OurBusiness-accounting, or OurBusiness-security)
If this is possible, what are the limits to the number of organizations that can be associated with the account? Are there any additional costs that this would entail? Are there any best practices to consider?
Also, is it possible to use an OAuth Service across organizations?
i.e. we would like to have one Authorization proxy (OAuth/OAuthV2) in a single (parent) Organization. All the other Organizations would use it but still maintain their own "Developer Apps" and "Products"?
I'm pretty sure its not possible as the "Developer Apps" id and secret seem to be Organization specific, but I thought I would double check anyway...
LinkedIn
Twitter
