Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 90
    • Issues 90
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 48
    • Merge requests 48
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Merge requests
  • !1890

Open
Created Dec 01, 2022 by eds-collabora@eds-collaboraContributor
  • Report abuse
Report abuse

User APIs for automated management

  • Overview 2
  • Commits 1
  • Changes 1

This adds three new XMLRPC user management APIs:

  • system.get_all_users to find out which users are registered on this LAVA instance.
  • system.set_user_active to lock and unlock accounts on the LAVA instance.

Both APIs require a token from a user with staff access. This uses the same @check_staff decorator as !1854 (merged).

The background here is our ongoing attempt to integrate LAVA more fully into a SSO environment, where OIDC only takes us so far in terms of things like account locking and access by use of user tokens.

Edited Dec 16, 2022 by eds-collabora
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: wip/eds/at9259/group_apis_upstream