Hi, Please try using uaa endpoint in userAuthorizationUri instead of login one. Thanks

HI, I think this change is important and need to be done, I like the new context parameters but not sure about the `optional`, I think it's important to which env. / platform we are talking too. Thank

Nice ! Hope this release will be able to make it. wrote:

Nice! Thanks for the broker ! wrote:

Welcome. marcela.bonell.manjarrez(a)intel.com> wrote:

Thanks Shannon ! that's a pretty good news hope we can increase perf more. :)

Hi Jason, You can take a look here https://www.cloudfoundry.org/250k-containers-in-production-a-real-test-for-the-real-world/ wrote:

It was a pleasure to work with Jim as well as colleague and as OSS contributor (firehose-to-syslog). Jim always help us to bring the best to the loggregator.

Well the impact of the WAF itself is minimal, due to LUA / Nginx (OpenResty). To be honest is still a POC but it's quite promising as now we don't have to care about runtime / docker things.

Hi Guillaume, I made a POC using route-service if you are interested https://github.com/shinji62/waf-cloudfoundry-route-service

I think for forget the link ??

Guillaume, Are you planning to support for nginx and apache ? How are you going to maintain the rules ? Thanks

Good job. wrote:

Maybe you should contact the pivotal support. https://support.pivotal.io/ wrote:

You can take a look at https://github.com/pivotal-cf/pcfdev. Thanks wrote:

How the pws / cloud-ops team verify the buildpack checksum before deploying it ?

Hi, Any json feed /api ? Can be nice and more easy to integrate with any CI/CD tool. Thanks wrote:

Hi, Marketplace is a CF things for CF so what is exaclty the problem you try to solve ?

marketplace is CF ....

These are env. variable in Go you can easily get it with os.Getenv(" VCAP_SERVICES") or you can use go-cfenv [1] as helper. [1] https://github.com/cloudfoundry-community/go-cfenv/