Versions Compared

Old Version 2

changes.mady.by.user Mikaël Geljić

Saved on

compared with

New Version Current

changes.mady.by.user Mikaël Geljić

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Avoid polluting User, MgnlUser APIs with non-security-related concerns
  • Enable external users to set magnolia and/or admincentral preferences
    • Allow easy bridging / mapping between external system user info and magnolia's user prefs 
  • Provide it as a backbone for public user profiles (via PUR)
  • Allow developers and templaters to consume user info

...

Here's a summary of what belongs where:

User / securityPreferences / profile
  • name
  • password
  • enabled
  • groups/roles
  • email
  • title
enabled
  • language
  • time zone

and potentially...

  • additional personal details
  • avatar
  • favorites
  • app-launcher settings
  • notification settings
  • content view settings (e.g. tree density, thumbnail size)

(question) Is email *just* a profile information? (accounts are usually bound to a single email as identifier)

(question) *Some* preferences may be provided by 3rd party systems too, do we consume them and/or allow to override them?

Where to go from there...

...

  • (question) Going further, should we go as far as having multiple workspaces per user entities, i.e. favorites in their own workspace?
    • calling for a workspace permission scheme to easily setup workspace ACLs and UI behaviors, when content shouldn't be shared between users

 

...