Filip, Does the uaa have a cli? It seems like uaac is a "cloudfoundry" thing. Sound like cli interactions are expected through curl. PS: wasn't sure where to ask this question since the UAA is a

I have been blocked by this issue for two weeks, and have no progress. I am looking forward to you to solve this problem. Thanks a lot. 2015-05-27 9:11 GMT+08:00 Dmitriy Kalinin

Thanks Dmitriy! Alberto Twitter: albertoaflores

Sure feel free to leave comments on the issue ( https://github.com/cloudfoundry/bosh-notes/issues/8) or file a PR against that document and I will try to incorporate it. wrote:

Thanks for the response! +1 on the "bosh-director.DIRECTOR-UUID.admin" scope. I assume this means that in the event of multiple directors, users will have to have multiple scopes associated to their

I've added a bosh-notes page about UAA integration: https://github.com/cloudfoundry/bosh-notes/blob/master/uaa.md (and associated issue: https://github.com/cloudfoundry/bosh-notes/issues/8) wrote:

We will ask the UAA team to start producing uaa-release shortly, which will be independent of cf-release. Eventually I expect people will remove uaa job from cf-release and just use

Love it! I'm wondering what are your thoughts for authorization? Wondering if the Director will introduce roles of any kind... Alberto Twitter: albertoaflores

True - silly me. Sounds great :) -- Neto

The UAA doesn't depend on CF, it can be leveraged as a stand alone product. aristoteles.neto(a)webdrive.co.nz> wrote:

From the perspective of using BOSH without CF, moving the users to the manifest is actually an improvement, as it allows you to list the actual users without logging in to the DB. Are there any plans

Sounds great! I assume you'll use a uaa oauth scope to determine if the given user actually has access to bosh? bosh.admin? wrote:

Hey all, We have resumed BOSH & UAA integration work: https://www.pivotaltracker.com/n/projects/1285490 to be worked on by a single pair. As part of this work we are going to provide two options how

Please see solution in this thread: https://lists.cloudfoundry.org/pipermail/cf-bosh/2015-May/000112.html We have a story at the top of the backlog to fix

Not to my knowledge. wrote:

Hi All, Post a sudden restart of Bosh director (due to issues with cloud provider), bosh vms command started giving http 500. Below are some observations and logs. Appreciate any help on this: $ bosh

Isn't it wrong that ping to google.com goes out of 216.59.196.14 address but ping to rubygems.org goes out of 10.0.0.2? Looks like routing or default gateway settings is broken on that machine. Check

Thanks Dmitriy – this fixed our issue J Sent: 26 May 2015 19:54 To: Scott Taggart Cc: CF BOSH Mailing List Subject: Re: [cf-bosh] Most bosh director commands fail with a HTTP 500 There

looks like you have a firewall or network connectivity issue between your OS and the destination, in this case rubygems.org. i would talk to your network administrator. for example, this is my curl

It solved the issue. Thank you very much! -- View this message in context: http://cf-bosh.70367.x6.nabble.com/cf-bosh-Multi-AZ-CF-Deployment-in-Openstack-tp64p67.html Sent from the CF BOSH mailing