Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 669
    • Issues 669
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 100
    • Merge requests 100
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #1478

Admin scopes BE handling

Origins: pleroma-fe!1032 (merged), pleroma-fe!1034 (merged)

Questions to discuss:

  1. Once PleromaFE develop branch receives support of admin scope (pleroma-fe!1034 (merged)), what do we do with previously issued PleromaFE apps / authorizations / tokens?
  • add admin scope to PleromaFE app records?
  • delete PleromaFE authorizations / tokens belonging to users with is_admin flag (so users need to sign in again) or append admin scope to them?
  1. What do we do once user is promoted to admins / downgraded from an admin to a regular user?
  • sign user out from all applications?
  • other
  1. Only allow admins to obtain admin scope?
  • assumed yes, but there is an alternative suggestion: pleroma-fe!1034 (comment 48315)
Assignee
Assign to
Time tracking