Ok, thanks for the helpful links. I replaced my config with the uaa.yml and login.yml from there and now the uaac commands from above work and I can run 'uaac token owner get'. I still can't login to

Minimalist defaults are in the UAA repo (uaa.yml and login.yml) https://github.com/cloudfoundry/uaa/tree/master/uaa/src/main/resources Yaml is very sensitive to indentation. So hand crafting it may

is there an example somewhere of a minimalist working config for them? I'm going through at the moment and trying to make mine resemble the

ok, that tells me that your configuration of the UAA clients is incorrect

Aha! Thank you very much. We have been working on network issues but I think for the interim I will up the cf_push_timeout.

ok so the 'uaac token client get' fails, and the error is 'Bad credentials'

ok, so we can validate that uaac target http://localhost:8080 uaac token client get admin -s <your admin client secret> uaac clients Should show your 'cf' client in the list then we can do uaac

On behalf of the Lattice AND the Routing teams, I am pleased to announce v0.4.0 of Lattice! We've taken some time off to convert our pipelines from GoCD to Concourse, and the Routing team has

I started the uaa by building from the tagged version in cf-release v215 and running it via tomcat with a custom config file, but I didn't specify a database. I have both a cf and admin section in the

ok, so the URL you have is /oauth/token, that's fine. your trace returns "authorization_endpoint":"http://localhost:8080","token_endpoint":" http://localhost:8080/uaa" indicating that there is a

Running that command against /uaa/oauth/token gives just a redirect to /login. Doing it with /oauth/token gives a 401 unauthorized, same as the cf cli. What do you mean by deploy it as root "/"? As

Oddly, I can see your list on nabble here: http://cf-dev.70369.x6.nabble.com/So-many-hard-coded-dropsonde-destinations-to-metrons-tp1474.html But it's just blank in the email, and also on the

ok, this should be an easy one to test (put in your username and password) curl -v -XPOST -H"Accept:application/json" -u "cf:" -d "username=marissa&password=koala&client_id=cf&grant_type=password"

Also: when i do 'uaac token get' with those same credentials, it succeeds.

curl exit code 6 means DNS failed. xip.io is flaky, so we this often in our dev environments where our app domains tend to be HA_PROXY_IP.xip.io. The CATS expect the apps to finish uploading,

Turn on trace, and post your data here. remember, if this is a prod environment, you may want to send me the token directly We can show you how to decode this token, and see why it is

I'm having an issue with my cloud controller/UAA setup where when I do cf login I get '401 unauthorized' back, but when I use the uaac command line tool to get a token it works fine. This makes me

johannes, the problem of upstream schema changes causing downstream change or breakage is the current situation: every addition of a metric type implies a change to the dropsonde-protocol requiring

Good afternoon! Our CF deployment fails 4 of the CATs. I have put the errors and the full output in a GIST here: https://gist.github.com/qanx/677d64df27d911f39acd Summary: * There's a curl error

Great! Thanks Dieu. Mike