Berkano

Refactoring - better SOC in user api

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: user
  • Labels:
    None
  • Number of attachments :
    0

Description

Currently, the user api is very much DAO centric. As a matter of fact, we only have DAOs.
Instead, mimicking os-user, we should have different "services" or "managers" for

  • authentication (getting basic user info, verifying identity)
  • membership (groups/roles)
  • profiles (currently called "properties" , for groups and users)

This should much more flexibility, for instance, having auth and membership backed by LDAP and profiles by an hibernated db, etc.

Issue Links

relates to

New Feature - A new feature of the product, which has yet to be developed. BERKANO-34 Add a way to check if a user is a member of a given group

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Grégory Joseph made changes -
Field Original Value New Value
Link This issue is related to BERKANO-34 [ BERKANO-34 ]

People

  • Assignee:
    Grégory Joseph
    Reporter:
    Grégory Joseph
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: