Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
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
  • #3612

Closed
Open
Created 12 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Password reset token is always invalid

Closed

Password reset token is always invalid

Created by: sashkab

User requests password reset. He gets an e-mail with link.

http://somethinglab/users/password/edit?reset_password_token=L6T4XPDTgsnTpA6ky9rr

New page opens and user enters new passwords twice. Upon clicking submit button, user get an error message:

1 error prohibited this user from being saved: 
Reset password token is invalid

GitLab 5.0.1, Ubunut 12.0.4

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: Razer6

      @sashkab Can't reproduce on 5.1 stable. Is it still an issue?

      By Administrator on 2013-05-12T17:05:58 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: sashkab

      It's fixed in 5.1 and this ticket can be closed.

      By Administrator on 2013-05-12T18:36:13 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: Razer6

      @sashkab You can close your own issues by yourself ;) /cc @senny

      By Administrator on 2013-05-12T19:02:35 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: sashkab

      Fixed in 5.1

      By Administrator on 2013-05-12T23:26:42 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: bon

      I'm getting this error in Gitlab 7.2.1.

      Should this issue be reopened or should I open a new one?

      By Administrator on 2015-01-27T17:54:28 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: sashkab

      You should upgrade to latest version first, ie 7.7.1 and see if it works for you. If you still will have issues - open new issue.

      By Administrator on 2015-01-27T18:04:25 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: bon

      the error is still present in 7.7.1. Could it be due to an interaction with the http server?

      By Administrator on 2015-01-29T07:42:43 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference:

    Menu

    Projects Groups Snippets
    Help