[Long term] Improve config UI

Story, context and use cases

• Goal: UI improvements to facilitate configuration and prevent admins from unwillingly changing settings leading to breaking an active LDAP config.
• Related
  • https://github.com/owncloud/user_ldap/issues/27
  • https://github.com/owncloud/user_ldap/issues/86

Product design concept

• Rewrite UI

  • start with listing of server conigurations
    • allow adding, removing, enabling, disabling of individual configs
    • give stats (# of users / groups)

• Rewrite config storage

  • dedicated config table instead of generic key value
    • makes code ausier
    • makes adding config options harder (schema migration)

Flow

1. Configure server connections
2. Check connection
3. Exemplary user is pulled from LDAP => Admin configures mapping
4. Further settings? Groups?
5. Finish and activate (config is fixed)

• Need a check for 'LDAP Query' parameters

• Users / Login attributes

  • Clearly separate LDAP query for users and for login
    • Users: Object + Group
    • Login: e.g. cn=%uid in addition to the Users filter

• Editing configs

1. Ability to copy config set
2. Edit
3. Save and activate

Technical concept

TBD

@felixboehm @butonic @felixheidecke

The issue names no files, tests, or entry points; begin by reviewing related issues #27 and #86 and the configuration flow described here. The technical concept is still TBD, so completion requires an agreed design covering configuration storage, connection checks, mappings, and activation before implementation can be scoped.