Precue Authentication mechanism(s)
Registered by
klap-in
Lyricue hasn't any registration of users. So Precue should handle its own users. Which authentication backends are desired? Also defining different user roles is part of the disccussion here.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Authentication:
- mysql database (default)
- LDAP (personal interest - Klap-in)
User roles:
- admin - add/delete/edit everything and set configuration
- moderator - add/delete/edit everything
- user - reads everything, add/edit songs and manage playlists
- readonly - reads everything. No editing.
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
