And finally I did a mapping of uaa.yml property names to config keys in the API, and uaa is hitting my server. Problem solved. wrote:

The file in the WAR file I'm using is called "ldap-groups-null.xml", but changing that still didn't fix the problem. There are a fair # of discrepancies between the property names in the uaa.yml file

This log entry might point to the problem. Will investigate... c-7] .... ERROR --- HomeController: Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML

I'm trying to use the UAA API to add an LDAP server dynamically, compared to specifying one in uaa.yml and restarting uaa. In the YAML file I had to set spring_profiles to "postgresql,ldap" I

Congrats! This is a huge release! ^5 team on the amazing work! wrote:

Congrats! It's awesome to have a decent CC API implementation that's properly maintained. Regards, Daniel Jones - CTO +44 (0)79 8000 9153 @DanielJonesEB

I'm immensely pleased to announce Cloud Foundry Java Client `2.0.0.RELEASE`! This release is the culmination of 54 weeks of work, encompassing 10 milestones, two release candidates, and 2,344

Hi Hector, If you are able to configure consul-release to (a) not rewrite /etc/resolv.conf and (b) not listen on port 53, then I assume you would run your own thing like bind or dnsmasq there, and

Yeah, that would be the minimum required. Then, I would add: (3) override the recursors to be used by consul. With those 3x options, consul can be configured to support any scenario without having

Hi All, I have put together a slide deck explaining a few routing use cases based on my understanding of the traffic flows in Cloud Foundry. Please feel free to point out any missing/erroneous flows

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.

We're planning on the next cf-release bump. At this time, both formats are supported, to allows the change to happen.

At what version does this change occur?

Hi Everyone, We have made changes to the way *uaa.scim.users* and *uaa.scim.groups* can be specified in the deployment manifest. The *previous* format for uaa.scim.users was: -

Hello all, Jim Campbell, the Project Lead for the Loggregator team within the Runtime PMC, last day at Pivotal was this week. We wish him well in his future endeavors and thank him for his time with

Hi, Jiaxin, Let's handle these cases separately. When you shut down a DEA or a Diego Cell gracefully (say, as BOSH does when updating or deleting a VM), it will attempt to get replacements for its

when you use bosh to update the runner vm, the instances will automatically migrate to another runner vm. You need to make sure you have enough vm(to be more specifically the resources ) to hold

I want to increase runner VM or delete runner VM. When I increase runner VM , I wish to make instances running on different VMs. When I delete runner VM , I wish to migrate instances from that VM to

Dingo PostgreSQL is a service broker that offers dedicated HA PostgreSQL clusters running in Docker containers, deployed & upgraded by BOSH. Continuously archiving all day long to Amazon S3. Batteries

CVE-2016-5016 UAA accepts expired certificatesSeverity High Vendor Cloud Foundry Foundation Versions Affected - Cloud Foundry release v239 and earlier versions - UAA release v3.4.1