Page tree
Skip to end of metadata
Go to start of metadata

Your Rating: Results: 1 Star2 Star3 Star4 Star5 Star 125 rates

Implemented in 4.0

Base roles included in specific modules where necessary.

Official Documentation Available

This topic is now covered in Default roles, groups and users.

Base roles included in specific modules where necessary.

Introduction

Currently we don't have a clear definition on which users, roles, groups we should provide and where we should put them to get them bootstrapped.

  • user tim is created in module in-place-templating but if you don't install the samples module where the base role is created your user tim would fail.
  • where should we create the base role?
  • where should users be created?
  • some roles are created when a new module creates a new repository i.e. resources module (resources-base role) templating module (templating-base module)

Open issues

  • No labels

6 Comments

  1. imo:

    • base roles should always be created/bootstrapped by the appropriate module
    • they should have a good name, and a fitting description (The "Base role allowing users to" prefix is probably redundant)
    • we might want to have an api to create such roles/ACLs rather than bootstrap files, thus making their maintenance easier (i.e we can simply read the code to understand what a role does)
    • sample users (such as Tim) are indeed samples.

    user tim is created in module in-place-templating but if you don't install the samples module where the base role is created your user tim would fail.

    As far as I can tell from the source, this is the other way around: the user is in bootstrap-samples, and the base role is always created.

    1. In general I agree. But we might want to bring few sample users with the demo project too. I think especially about an editor.

      1. Absolutely. See MGNLSTK-246@jira - there are currently some in m-m-samples.

  2. Bad wording:

    user tim is created in module in-place-templating but if you don't install the samples module where the base role is created your user tim would fail.

    should say: the base role base theat allows users to access to website content and get&post requests is added in the samples module, Tim is created in inplace-templating and referencing to the base role created in the samples module. No samples module and Tim role displays just a uuid.

    1. it's still not very clear (big grin)

      Do we want to refer to roles by name instead of uuid? (which would be consistent with what we do for templates, dialogs etc)

  3. This page is missing the {status} macro.