True Serverless Applications Implementing Cloud Native Access Control Service
summary
Centralized, cloud-native serverless access control called advocada implements policy-based, record-level ACLs with prohibitive rules and a guard+advocate enforcement model; it stores policies in PostgreSQL/MongoDB, exposes a REST API and a browser UI, and runs on Java 16 with Spring Boot. Project starts summer 2020, delivers PoC on 2020-09-09 and an MVP 1.5 months later, grows from three juniors to a team of ~7 developers plus mentors, and is used internally at EPAM with Keycloak integration and folder/version services on the roadmap.
AI-written summary · about
chapters (18)
- 0:00Start
- 13:40What is Advocada?
- 16:08Why we need?
- 17:38Enterprise Architectures As Of Today
- 20:32Policy Based Record Level Access Control Service (ACS)
- 22:12Policy is assigned to Resource
- 26:05Policy Example
- 26:41Access Control List=SUM( Access Control Elements)
- 31:28Access Control Request
- 33:26Every Project Needs Developers
- 35:00Project Structure
- 36:27Minimal Valuable Product
- 38:14Listing ACL Types
- 40:53Selecting an Action
- 42:39KeyCloak from RedHat
- 44:28Roadmap Vision
- 46:27Business Agnostic Business Services
- 50:28Takeaway, Summary
related talks
39mAttribute Based Access Control Framework for IoT
31mSecure-by-Default Spring Apps: Zero Trust, OAuth2, and Runtime Policies
20mBuilding Scalable Access Control Frameworks in React
35mOPA: The Cloud Native Policy Engine
43mApplication Code of Conduct - Full-Stack Policy as Code
30mHeard you liked access, so we built Access to...
20mCoordinated Access Control with @policy
25mModernizing Authorization: From Basic Roles to Decoupled ABAC