Thanks for the clarification. Would you recommend using only the role methods on the organization resource (as opposed to on /users/) as a general rule? Just for my own understanding, would it be

If this is your first local set-up attempt, I encourage you to do it using bosh-lite. You can find very comprehensive information in the READMEs on setting up bosh-lite

Hi Ivan, I have tried, it's not working. I am following this <https://groups.google.com/a/cloudfoundry.org/forum/#!msg/vcap-dev/IC8U-AdtPLg/Mq02EvPsJBAJ> for uaa setup and configuration. As per

Hi Pravin, Have you tried cf auth admin admin as suggested in the bosh-lite

Hello All, I am doing local setup of cloud foundry golang clinet, cloud controller ng, uaa and nats. So far I have configure all and it's communicating to each other. Now when I am doing target: cf

Hi Daniel, The purpose of the Associate User with the Organization endpoint is to add a user to an organization. This endpoint needs to be called before a user can be added to the organization's

Thanks Nick and Mike for the details. I am curious to know if the issue had been pinpointed by the bosh team, and whether the fix would be purely in bosh or require adaptation of cf-release. Looking

We discovered this fix out of sheer luck. So, no help there sorry. :) Mike

Hey Guillaume, To be fair, this did take some time to figure out on our end. It has to do with the interaction between BOSH and Monit. As Dieu mentioned, runtime has a story to potentially determine

It looks like we were making this harder than it needed to be. Grepping through the

hi Bob, you can still leverage an outside login server, none of the endpoints to accommodate have changed. We are 100% backwards compatible. I don't believe that we ever stated that we would not use

Filip, When the uaa and login were merged it was state that replacing replacing the login server would remain a supported scenario and this seems a departure from that statement. At the very least,

hi Sree and Matt, Matt is actually not referring to the wild cards. He wants the login.<domain> for his own application. Matt, at this time we are claiming that domain name, as we did with the login

Hi Matt, This new wild card route pattern was introduced for multi-tenancy in UAA post merge. Anything before login or uaa in the URL is now treated as a zone subdomain and the zone context is derived

Thanks again Filip, I got that resolved. Gradle needed my proxy settings to be entered here. $cat

Oups, sorry, I had probably overlooked this faulty trace that should have hinted me. [2015-05-26 16:37:51+0000] ------------ STARTING cloud_controller_ng_ctl at Tue May 26 16:37:51 UTC 2015

Thanks a lot Mike and Dieu. Indeed moving the nfs_mounter last seemed indeed to fix the issue in v207. If ever this reproduces on master and can help, I submitted

Hi all, I'm working on some automation for my client to declaratively configure orgs and spaces across multiple Cloud Foundry instances (hopefully they'll permit open-sourcing this). I erroneously

Hi, Thanks for the response. It seems to get stuck here .. ./gradlew assemble --info Downloading

Prior to the consolidation of uaa and the login server in uaa release 2.0, we were running our own login server to handle auth to our platform. We simply reduced the instance of the bundled CF login