"Our quest for ACL improvements in TYPO3 Core"
summary
A year-long research plus a community survey surfaces missing best practices and a pain point: permissions live as DB user/group records so they cannot be version controlled. Concrete changes land in core (some patches pending): default user groups created at install (since 13.1), a combined Access/Permissions backend module, split record/module tabs, a form-preview for excluded fields, a two-column read/write UI and a user-assignment editor. A prototype for extension presets applies extension-defined permission sets; full deployable permissions (exportable/versionable) targets a later release (likely v14).
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 1:11Research and community survey
- 5:53Permission best practices
- 13:59Default user groups in TYPO3
- 14:44User experience improvements
- 22:48Next steps and future plans
- 26:43Q&A session
related talks
05mACLs and Sharing
42mEssential Solutions for TYPO3 Productivity - Part 2
45mUnder Odoo's Hood: Secrets of an unbreakable permissions architecture
26mCan It Be Done? Building Fine-Grained Access Control for Back...
48mHacking TYPO3 - a journey through recent security vulnerabilities
27mLessons Learned Implementing Meaningful Access Controls...
21mSecuring Backstage Plugins Using the Permissions Framework
30mFuture Paths for the OpenSearch Security Layer