We have a separate instance of UAA server interacting with the MySQL database running on cloud.gov. Recently, we have been advised to use a TLS connection to connect to the database. After doing some

Hi all! Many thanks to those that helped with the early functional testing of the new CFCD v2 exam! We've moved into beta testing now, and are looking for people that want to attempt the certification

Hi, everyone, Pivotal is nominating Dan Beneke for the UAA Project Lead in the Application Runtime PMC. Dan Beneke is a Senior Product Manager at Pivotal who has been working on identity topics within

Hi, everyone, Chao Wang, the Project Lead for the UAA team within the Application Runtime PMC, has stepped down from the project, as he has recently left Pivotal. We thank him for his service. The UAA

[cross-post for visibility on cf-bosh and cf-dev. Sorry for the spam if you're reading both lists. Future posts about this will be sent to cf-bosh only.] Dear Friends of BOSH, As the

Hello cf-dev! We have cut routing-release 0.190.0Release Highlights Jobs consuming the routing-api link do not fail when routing-api is not present details Routing-API supports deletion of Router

Hi everyone, The cf CLI team reached out to the Community back in December 2017 to gather feedback about domains and hostnames app manifest properties. Based on feedback, in cf CLI release v6.34.0,

Hello cf-dev! We have cut istio-release 1.3.0, here are the release highlights: Release Highlights - App developer can rely on the platform to provide client-side load balancing for app to app

I added a console setup and removed the file setup before compiling and it works. appender.console.type = Console appender.console.name = STDOUT appender.console.layout.type =

+Joshua Casey who is the master of Log4j2

Thanks Chaos. The doc says to create a custom env logging.config and point to log4j2 format file. Just like in the previous versions, why can we not get the logging by default ? Should I just create

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