Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #3720

Closed
Open
Created Apr 24, 2013 by Administrator@rootOwner

Increase data manipulation on User API to include all user properties.

Created by: minorOffense

Right now, when you GET the current user you have access to the following data:

  "id": 1,
  "username": "john_smith",
  "email": "[email protected]",
  "name": "John Smith",
  "private_token": "dd34asd13as",
  "blocked": false,
  "created_at": "2012-05-23T08:00:58Z",
  "bio": null,
  "skype": "",
  "linkedin": "",
  "twitter": "",
  "dark_scheme": false,
  "theme_id": 1
  "is_admin": false,
  "can_create_group" : true,
  "can_create_team" : true,
  "can_create_project" : true

Which differs from the data when loading an arbitrary user.

However when manipulating users (i.e. insert/update) you only have access to the following values:

    email (required) - Email
    password (required) - Password
    username (required) - Username
    name (required) - Name
    skype (optional) - Skype ID
    linkedin (optional) - Linkedin
    twitter (optional) - Twitter account
    projects_limit (optional) - Number of projects user can create
    extern_uid (optional) - External UID
    provider (optional) - External provider name
    bio (optional) - User's bio

Notably missing are the options to block users, set the dark scheme, marking the user as an admin.

Beyond that, having access to the user's API token via a service call would be useful as well. Giving a means to completely controlling users via the API.

Assignee
Assign to
Time tracking