Project

General

Profile

Actions

Epic #95904

open

Make backend user and user groups deployable

Added by Oliver Bartsch over 2 years ago. Updated 8 months ago.

Status:
Under Review
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2021-11-08
Due date:
% Done:

0%

Estimated time:
Sprint Focus:

Description

This issue was raised during the T3MC session "Zap the gremlins".

The issue has been discussed in April 2022 in the #typo3-cms-coredev channel (https://typo3.slack.com/archives/C03AM9R17/p1650369198186799). The following is the result of the discussion.

General requirements

  • preferred format: YAML * core uses it already * can be commented
  • definitions can be shipped with extensions
  • the functionality can be compared with the handling of Site configuration * Site configuration (still) has implicit dependencies on UID values in `rootPageId` and `limitToPages` (for route enhancers) * replacing those UIDs by distinct / universally-unique seems to be a good way to go
  • events should be provided * as with the Site configuration * allows extension authors to hang in there dynamically before / after the cache building
  • overwriting / modification should be simple * it is a no-brainer to inherit the default "news editor" and remove some fields or add another backend module
  • error handling * handle defined but missing relations to groups and mounts

User Groups

  • groups should be understood as roles, e.g. "news editor"
  • a role * includes corresponding permissions (= contains the access control) * should be assigned to a group (= collection of roles)
  • a group * will be assigned to a user * contains the DB and file mounts
  • be_groups needs an additional string identifier to avoid relying on autoincrement IDs
  • we recommend a human readable string identifier which helps to handle those definitions

Problems to be discussed

  • using string identifiers do not guarantee uniqueness -> having a UUID could solve the problem but causes additional work on datahandler (which considers everything not a UID to be a new record placeholder, if it starts with NEW)

Users

  • handling of one or more user records

Problems to be discussed

  • handling of sensitive data (passwordl, name, email address)

Handling user groups would solve a big problem and would be a huge improvement. The import and export of users is rather complex, the value small.

There are some solutions already out there:
Actions #1

Updated by Oliver Bartsch over 2 years ago

  • Tags set to t3cm
Actions #2

Updated by Björn Jacob about 2 years ago

  • Description updated (diff)
Actions #3

Updated by Björn Jacob about 2 years ago

  • Description updated (diff)
Actions #4

Updated by Björn Jacob about 2 years ago

  • Description updated (diff)
Actions #5

Updated by Björn Jacob about 2 years ago

  • Tracker changed from Feature to Epic
  • Tags deleted (t3cm)
Actions #6

Updated by Björn Jacob about 2 years ago

  • Description updated (diff)
Actions #7

Updated by Josef Glatz almost 2 years ago

Here's the fork initial from Michiel which works with TYPO3 10.5 LTS: https://github.com/supseven-at/t3ext-yaml-configuration. I have updated all the things with a limited feature set for 9.5 and 10.5

Actions #8

Updated by Albrecht Köhnlein almost 2 years ago

And here is the link to Benni's tool: https://github.com/bmack/site-importer

Actions #9

Updated by Gerrit Code Review almost 2 years ago

  • Status changed from New to Under Review

Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75007

Actions #10

Updated by Gerrit Code Review almost 2 years ago

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75007

Actions #11

Updated by Gerrit Code Review almost 2 years ago

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75007

Actions #12

Updated by Oliver Hader almost 2 years ago

Has been published recently: https://github.com/b13/permission-sets

Actions #13

Updated by Gerrit Code Review almost 2 years ago

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75007

Actions #14

Updated by Hannes Lau about 1 year ago

Hi Andreas! Hi All! I was excited to see this issue, as I would love to version user groups in git. Yet, when I look at the patch set, I get the impression that I would still have to create a database record for every user group that I create in git. This would (at least) partially defeat the purpose of versioning user groups in my site package. Would it at all be feasible to make the versioned user groups directly selectable for be_users?

Actions #15

Updated by Gerrit Code Review 8 months ago

Patch set 5 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75007

Actions

Also available in: Atom PDF