Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 197
    • Issues 197
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #80

Closed
Open
Created Oct 29, 2019 by Vicky Risk@vickyDeveloper2 of 4 tasks completed2/4 tasks

Req 10.3 - User authorization

As an administrator, eventually I will need fairly fine-grained control over user access and privileges, particularly to:

  • limit configuration authorization to confined areas of the network. (this is meant in reference to making changes in Kea servers via Stork)

  • Initially, if I can have system-wide read-only, read-write, and super user privilege levels, that would be adequate.

  • Read-write would include adding devices to Stork to be monitored and making most configuration changes in Stork. (it's called admin)

  • Super user privileges would include creating new users and giving them read-write privileges. Read-only would be for people who just have the ability to navigate the dashboard and view alerts, alarms and statistics.

Edited Jan 18, 2022 by Vicky Risk
Assignee
Assign to
Time tracking