Extending Cloud Foundry UAA
summary
Warner Music extends UAA by running two UAAs (one vanilla, one modified as a Cloud Foundry app) that authenticate against Active Directory and persist to Cassandra instead of Postgres. Architecture uses full, separate Cloud Foundry deployments per data center with Cassandra multi‑DC replication, favoring local reads and global writes and moving toward one Cassandra cluster per application stream to avoid terabyte‑scale contention. Teams also build a web Cloud Console for onboarding and managing apps; it’s in production.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker background
- 2:53UAA role in Cloud Foundry
- 7:04Multi-data center architecture
- 13:03Migration to Cloud Foundry v2
- 15:53Separation of apps and services
- 16:38Cloud Console demo and purpose
- 21:57Q&A on UAA integration and open source
related talks
37mDeploying UAA to Cloud Foundry and using within your Applications
39mCloud Foundry UAA as an Identity Gateway
31mCloud Foundry UAA as an Identity Proxy Product Roadmap
08mUser Story
31mUser Account and Authorization Server at SAP
36mMulti-Cloud with Cloud Foundry: Making It Real - Dmitry Bakaleinik, SAP & Sean McKenna, Microsoft
21mA Roadmap to Active Multi Cloud
32mBuilding a Robust Cloud Foundry (HA, Security and DR)
