Please use the next version of CF-Deployment as we have identified an issue with UAA version 73.4.0 due to a backward incompatibility issue in upgrading to Spring Security 5 on 07-19-2019. The next

Hi Viraj, Please check the release notes of UAA 4.31.0 which shared the changes you need to make, there are also additional comments from the tracker story if you need more details. Thanks, Chao

When I was using UAA 4.30.0, UAA used to log a lot of messages which was fine. However, I recently upgraded the UAA to 4.35.0 and the logging stopped working. I deploy UAA by getting the source from

hi Enrique, The port number will not be forced if the appropriate proxy headers are set *AND* the request comes from a trusted IP (Tomcat's RemoteIpValve) ie, the HttpServletRequest.getScheme

Dear Cloud Foundry Community, Please let me or Karthik know, if you’d like to bring any specific topics for discussion for the next sig meeting on Wednesday, June 24th at 08:00 US Pacific | 11:00

Happy Friday everyone, CF-deployment v10.0 is now live. Please refer to the release notes for breaking changes: https://github.com/cloudfoundry/cf-deployment/releases/tag/v10.0.0 Let me know if you

Thank you, Filip. We are not using uaa-release, and we can control the protocol (https). Our issue is that the port number is forced to be 443 when we don't want that to happen. Regards Enrique

Hi, everyone, Pivotal is nominating Allen Duet for the Loggregator Project Lead in the Application Runtime PMC. Allen is a Director of Product Management at Pivotal where he oversees Cloud Foundry

Hi, everyone, Fred Krone, the lead for the Loggregator project within the Application Runtime PMC, is stepping down from the project, as he has recently left Pivotal. We thank him for his

Hello cf-dev! We have cut routing-release 0.189.0. This release includes several fixes and improvements. Notably, this release encrypts the control plane interactions with the routing-api. Release

Good day everyone, We have an update on the scope for CF-Deployment v10.0. We are postponing BOSH Service discovery to the next major release. The changes require additional validation and will not be

request.getScheme() can return https properly if you configure the web server (Tomcat/Jetty) to trust the headers X-Forwarded-Proto based on the IP address of the proxy server. If you're using

FYI... see below —— Hi, all, Reminder that the CAB call [0] for July 2019 is next Wednesday 17th @ 8a Pacific. We will have regular highlights, QAs, as well as two planned talks: 1.

Hi We are running UAA behind an ingress controller on Kubernetes. The connection to the ingress controller is https on a port other than 443 e.g. 8443. The connection to UAA pod is http. The issue we

Pivotal doesn't have access. The CFF web team resolved this issue a week ago. Thanks! https://www.cloudfoundry.org/foundryblog/security-advisory/feed/ Chip Childers, CTO Cloud Foundry Foundation

Hi Lee, I'm forwarding your message along to the Pivotal security team to take a look. Thanks, Emily On Tue, Jul 2, 2019 at 12:05 AM Lee Porte via Lists.Cloudfoundry.Org

The first release of the Go buildpack after August 10, 2019 will no longer include Go versions 1.11.x These Go versions will no longer be supported upstream. Please migrate your Go apps to supported

The first release of the PHP buildpack after August 10, 2019 will no longer include nginx versions 1.15.x. These nginx versions are no longer supported upstream. Please migrate your PHP apps to

The first release of the staticfile buildpack after August 10, 2019 will no longer include nginx versions 1.15.x. These nginx versions are no longer supported upstream. Please migrate your staticfile

The first release of the R buildpack after August 10, 2019 will no longer include R versions 3.4.x and 3.5.x. These R versions are no longer supported upstream. Please migrate your R apps to supported