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
  • Merge requests
  • !10472

Closed
Created Feb 06, 2018 by Administrator@rootOwner
  • Report abuse
Report abuse

Add skip_password_expiration boolean when doing PUT on users

  • Overview 0
  • Commits 1
  • Changes 2

Created by: eLvErDe

Hello,

We're synchronizing users's password using admin API key and recent GitLab CE releases broke this behavior by adding an "already-expired-password" feature when a user's password is being changed throught the API. That leads to an unexpected password change prompt when the users logs in.

Altough I understand this feature I think our usage makes sense too and both should be allowed.

This pull request adds a boolean to override password expiration to the API.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/EarthLab-Luxembourg/api_skip_password_expiration_boolean