Sorry, all I used the "Raw text" function in Nabble, but it is not suitable for other environment. Thanks for telling, Amit. Amit Gupta wrote ----- I'm not a ... noburou taniguchi -- View this

I'll echo the Integration team's question. For what use cases do you want to register routes directly, rather than through the Cloud Controller API or cf CLI? The Routing API Mark mentioned also

those urls do not look right. but they are dependent on what url you deployed the uaa under. ( ie / or /uaa ) what's returned by uaac info is dependent on your uaa config. I'd have to get back to

I realize it's a pain, but I'm setting these up without bosh. I'm just unfamiliar with how the config between the CC and the UAA needs to be set. The http://localhost:8080/login and

ok, is that the correct URL? you're attempting to configure a very large eco system by hand. That can be a bit difficult. If you want a local cloud foundry, I would suggest bosh-lite basically,

The cloud controller logs have "Invalid bearer token: #<CF::UAA::InvalidSignature: Signature verification failed>" and the 401 invalid auth message.

Ok, I set those 2 properties to http://localhost:8080 and it looks identical; same error, same endpoints requested. Could something be wrong with the cloud controller config?

yes, this is the URL misconfiguration I was talking about. In your uaa.yml you should have two properties login.url: http://localhost:8080 uaa.url: http://localhost:8080 set those two, and let's

Sure. I added a note in the note story to consider that request. -Dieu

One other note to whoever ends up working on this issue. It would be great to add support in "cf push" and manifest commands as well. Mike

The CLI seems to be able to get a token now though, it's failing for a different reason: API endpoint: http://localhost:8181 REQUEST: [2015-09-04T20:46:51Z] GET /v2/info HTTP/1.1 Host:

Hi Lakshman, We are wondering why you would like to add routes to the gorouter? Unfortunately there is not any way to add these untill the routing api becomes part of the official release. The NATS

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