If you're using the common bosh lite IP of 10.244.0.34, you can also use the more-reliable *.bosh-lite.com

Yes, xip.io is flaky. I would recommend setting up real DNS if you want to avoid the 2% failure rate if you want a longer term, reliable solution. wrote:

Hi, Currently we see IO errors when trying to contact xip.io - this happens around 2% of the times. To apply a temporary fix - I updated the /etc/hosts of the ha_proxy VM to map the - IP to the

Hey Matt, Dieu's suggestion will fix your problem (you'll have to make the change on all CC's), although it'll get undone on each redeploy. We do want to find the root cause, but have not been able

Thanks for authoritive answer. My application is a Java (Spring Framework) one hence the solution with Spring Security is just fine for me.

Yep, this is not supported. Our recommendation is to do consolidation on the LDAP side. -Sree

It appears my issue was caused by this uaa issue: https://github.com/cloudfoundry/uaa/issues/223 Now to figure out the best way to work around it. Thanks for your help Matt. Mike

We have seen this with some node apps. Does your app or buildpack reference either of the following env variables VCAP_APP_HOST and

If your `access_token` value is 1. a client_credentials grant - the `oldPassword` field is not evaluated and can be omitted OR 2. it's a user token, with the scope of `uaa.admin` and the admin is

Thank You very much for info. For now I'm using slapd-meta backend (http://linux.die.net/man/5/slapd-meta) witch allow me to merge two trees in one tree. The AD I'm using is Samba 4 solutions. I was

Hi, The best approach is to use AD LS which can act as a proxy and consolidate the traffic from multiple AD domains https://msdn.microsoft.com/en-us/library/aa705886(v=vs.85).aspx Thanks, Sree

This is what I'm now seeing in the logs: ssh-proxy: {"timestamp":"1446134601.007453442","source":"ssh-proxy","message":"ssh-proxy.authentication-failed","log_level":2,"data":{"error":"no auth passed

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