Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #5788
Closed
Open
Issue created Mar 13, 2018 by bmortier@bmortierMaintainer

Failed lock attempt gives misleading error (password method does not support locking )

Description

When failing to lock a user (see plugin issue 5792) the error message tells me locking would be unsupported for the (currently used) password method, while locking seems well supported and only this attempt failed.

Distribution Name and Version

Debian / also present at demo.

FusionDirectory Version

1.0.19-1-debian, 1.2 (demo.fusiondirectory)

PHP version used

7.0+49 (Debian Stretch)

Origin of php packages

Debian Stretch

Steps to Reproduce

  1. Try to lock a user with a method that is bound to fail (e.g.plugin issue 5792)
  2. Click ok at the locking error
  3. See a warning password method XY would not support locking

Expected behavior:

At step 3: An error message that this locking attempt failed due to an unknown reason

  • Followed by a hint to workaround by manually e.g. setting a impossible hash / changing password method to unsupported SASL
  • Followed by a link to the issue-tracker perhaps.

Actual behavior:

Incorrect warning that had me wonder a second why SASL does not support locking out of the sudden while it worked last week : )

Reproduces how often: 100% (5/5)

Additional Information

Verified at a Debian stretch 1.0.19, Debian stretch with packaged 1.2 (OH by the way: Thanks for packaging!) and at demo.fusiondirectory.org

Assignee
Assign to
Time tracking