Hi Nicholas, many thanks for the doubt. I continue here: http://support.run.pivotal.io/entries/106222933-Problem-deploying-basic-Apps-on-PWS

As an admin, you can cf curl /v2/users https://apidocs.cloudfoundry.org/222/users/list_all_users.html

Hi, I was wondering if there was a (straigthforward) way to list all users instead of using the "cf org-users" or "cf space-users" commands. Thanks Remi

Hi Juan Antonio, Support for PWS is available here: http://support.run.pivotal.io/home Is your application a worker (one that doesn't respond to http)? If so, you should disable the health check

Hi, I am trying to deploy an Application on PWS and I think that the problem is something related with Diego. In previous weeks, I deployed without any problem to PWS but today, I receive the

About 66 responded to survey in the one week I kept it open. Best, Max — Sent from Mailbox <aleksey.zalesov(a)altoros.com> wrote:

Cool! Thank you for sharing How many people took survey? Alex Zalesov

I did the work on the cli plugin but not on the integration into the cli. Based on your first error, it looked like we were having a problem getting the one time code, not authenticating with the ssh

I think I'm getting closer. In UAA I now get the error: TokenEndpoint: Handling error: InvalidGrantException, Invalid authorization code: ad1o9o This must be someone trying to redeem the auth

That curl command returns what appears to be the correct response: curl -v -k -H "Authorization: $(cf oauth-token | tail -1)"

Thanks for taking a look, fingers crossed you can see it happen as well. Our 217 install is on stemcell 3026 and our 212 install is on 2989. IaaS is CenturyLink Cloud. -Matt

That's not the request that the plugin is making to get the token. We're using the API that was created for us [1]. If you use straight curl with something like this, what does the flow really look

I got up to 10k on an AWS deployment of HEAD of cf-release with ruby 2.2, then started another loop on the same box with ruby 2.1. In the end, they got up to 40-50k without showing any signs of

In case it helps this is the CF_TRACE of the UAA call that the ssh plugin is expecting to be a redirect. REQUEST: [2015-10-28T17:25:11-06:00] POST /oauth/token HTTP/1.1 Host: uaa.{redacted} Accept:

Yes /v2/info contains "app_ssh_oauth_client: "ssh-proxy"". Though I didn't set it. It appears CC sets it by default

Does /v2/info contain the `app_ssh_auth_client` key? If not, it should be set to the client ID of the ssh proxy. If it's not set, I think that's one of the

Thanks Matt, this is awesome. I'm trying to reproduce this with your script, up at 10k with no change. I'm also shelling out to curl in the script, to see if both curl and ruby get affected, and so,

I'm working on upgrading to latest cf-release+diego and I'm having trouble getting ssh working. When attempting to ssh with the latest cli I get the error: "Authorization server did not redirect

You might try moving the nameserver entry for the consul_agent in /etc/resolv.conf on the cloud controller to the end to see if that helps. -Dieu

Looks like you're right and we're experiencing the same issue as you are Amit. We're suffering slow DNS lookups. The code is spending all of its time