Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
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 39
    • Issues 39
    • 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
  • #1180
Something went wrong while setting issue due date.
Closed
Open
Issue created 12 years ago by bmortier@bmortierMaintainer
  • New related issue

  • New related issue

Pop-up error when locking/unlocking user

Closed

Pop-up error when locking/unlocking user

Hello,

When I lock or unlock a user in FD, I get this error:

@Command specified as saslRealm or saslExop hook for plugin 'SASL' does not exist! @

Howerver, the user is correctly locked (@!@ in its password)

(from redmine: issue id 1180, created on 2012-07-25, closed on 2012-08-09)

  • Changesets:
    • Revision cc5510bb by Benoit MORTIER on 2012-08-09T10:53:09.000Z:
Fixes: #1180 Pop-up error when locking/unlocking user
  • Revision 25245729 by Benoit MORTIER on 2012-08-09T10:53:50.000Z:
Fixes: #1180 Pop-up error when locking/unlocking user
  • Uploads:
    • 0001-Fixes-1180-Pop-up-error-when-locking-unlocking-user.patch
    • 0002-Fixes-1180-Pop-up-error-when-locking-unlocking-user.patch

    Tasks

    0

    No tasks are currently assigned. Use tasks to break down this issue into smaller parts.

    Linked items
    0

    Link issues together to show that they're related. Learn more.

    Activity


    • bmortier
      bmortier @bmortier · 12 years ago
      Author Maintainer

      Hum the error message may be not very clear but what it means is that you need to fill either saslRealm or saslExop in order for SASL method to work.

      Do you get the error even if you're not using SASL?

      (from redmine: written on 2012-07-26)

      By Côme Chilliet on 2017-09-02T14:47:08 (imported from GitLab)

    • bmortier
      bmortier @bmortier · 12 years ago
      Author Maintainer

      Côme BERNIGAUD wrote:

      Hum the error message may be not very clear but what it means is that you need to fill either saslRealm or saslExop in order for SASL method to work.

      Do you get the error even if you're not using SASL?

      I do not use SASL. I tried to install many SASL packages in my distribution (Debian stable btw), same error.

      On @fusiondirectory.conf@, the only SASL-related part is disabled:

      useSaslForKerberos="false"
      

      (from redmine: written on 2012-07-26)

      By rverchere on 2017-09-02T14:47:08 (imported from GitLab)

    • bmortier
      bmortier @bmortier · 12 years ago
      Author Maintainer

      It's weird, I really can't reproduce the problem. I've put saslExop and saslRealm to "", and now I only get this error if I lock/unlock a user that have sasl as password method. The other ones works just fine.

      Maybe it's already fixed in development version by some other patch?

      (from redmine: written on 2012-07-27)

      By Côme Chilliet on 2017-09-02T14:47:09 (imported from GitLab)

    • bmortier
      bmortier @bmortier · 12 years ago
      Author Maintainer

      Hello,

      i got the issue in the 1.0.4 branch i put debug log here

      0 file /usr/share/fusiondirectory/include/class_msg_dialog.inc line 117 function __construct class msg_dialog object OBJECT - msg_dialog type -> args 0 Error 1 Command specified as saslRealm or saslExop hook for plugin 'SASL' does not exist! 2 10003 1 file /usr/share/fusiondirectory/include/password-methods/class_password-methods-sasl.inc line 52 function display class msg_dialog type :: args 0 Error 1 Command specified as saslRealm or saslExop hook for plugin 'SASL' does not exist! 2 10003 2 file /usr/share/fusiondirectory/include/password-methods/class_password-methods.inc line 331 function __construct class passwordMethodsasl object OBJECT - passwordMethodsasl type -> args 0 OBJECT - config 1 uid=toto,ou=people,dc=labo,dc=opensides,dc=be 3 file /usr/share/fusiondirectory/plugins/admin/users/class_userManagement.inc line 797 function get_method class passwordMethod type :: args 0 {CRYPT}1gK5OQEw.$2VPx9RWGuxDJ3x.XBp3t21 1 uid=toto,ou=people,dc=labo,dc=opensides,dc=be 4 file /usr/share/fusiondirectory/include/class_management.inc line 432 function lockEntry class userManagement object OBJECT - userManagement type -> args 0 lock 1 0 uid=toto,ou=people,dc=labo,dc=opensides,dc=be 2 targets 0 uid=toto,ou=people,dc=labo,dc=opensides,dc=be action lock 5 file /usr/share/fusiondirectory/include/class_management.inc line 160 function handleActions class management object OBJECT - userManagement type -> args 0 targets 0 uid=toto,ou=people,dc=labo,dc=opensides,dc=be action lock 6 file /usr/share/fusiondirectory/plugins/admin/users/main.inc line 42 function execute class management object OBJECT - userManagement type -> args Array (empty) 7 file /usr/share/fusiondirectory/html/main.php line 364 args 0 /usr/share/fusiondirectory/plugins/admin/users/main.inc function require Error Error Command specified as saslRealm or saslExop hook for plugin 'SASL' does not exist!

      Trace uid=toto,ou=people,dc=labo,dc=opensides,dc=be

      (from redmine: written on 2012-08-08)

      By bmortier on 2017-09-02T14:47:09 (imported from GitLab)

    • bmortier
      bmortier @bmortier · 12 years ago
      Author Maintainer

      Hello,

      as you can see i'am in crypt in the user entry

      8 uid=toto,ou=people,dc=labo,dc=opensides,dc=be sn: test1 givenName: toto uid: toto dateOfBirth: 1992-08-05 gender: M preferredLanguage: fr_FR cn: toto test1 homeDirectory: /home/toto loginShell: /bin/bash uidNumber: 1101 gidNumber: 1101 gecos: toto test1 objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson objectClass: gosaAccount objectClass: posixAccount objectClass: shadowAccount sambaLMPassword: EBD223B61F8C259CAAD3B435B51404EE sambaNTPassword: 98BB35737013AAFF03181D0FE9FDA09E sambaPwdLastSet: 1344439993 sambaBadPasswordCount: 0 sambaBadPasswordTime: 0 shadowLastChange: 15560 userPassword: {CRYPT}!1gK5OQEw.$2VPx9RWGuxDJ3x.XBp3t21

      (from redmine: written on 2012-08-08)

      By bmortier on 2017-09-02T14:47:10 (imported from GitLab)

    • bmortier
      bmortier @bmortier · 12 years ago
      Author Maintainer

      This should fix it. It should be heavily tested as I changed an important part of password logic. (Basically I just switched some methods to static ones)

      (from redmine: written on 2012-08-09)

      By Côme Chilliet on 2017-09-02T14:47:10 (imported from GitLab)

    • bmortier
      bmortier @bmortier · 12 years ago
      Author Maintainer

      Try this

      (from redmine: written on 2012-08-09)

      By Côme Chilliet on 2017-09-02T14:47:10 (imported from GitLab)

    • bmortier
      bmortier @bmortier · 12 years ago
      Author Maintainer

      Close issue

      (from redmine: written on 2012-08-09)

      By bmortier on 2017-09-02T14:47:10 (imported from GitLab)

    • bmortier closed 7 years ago

      closed

      By bmortier on 2017-09-02T14:47:11 (imported from GitLab)

    • bmortier added Fixed PJ1802-0188 fusiondirectory-core labels and removed Bugs label 2 years ago

      added Fixed PJ1802-0188 fusiondirectory-core labels and removed Bugs label

    Please register or sign in to reply
    Assignee
    bmortier's avatar
    bmortier
    Assign to
    Labels
    0
    None
    0
    None
      Assign labels
    • Manage project labels

    Milestone
    No milestone
    None
    Due date
    None
    None
    None
    Time tracking
    No estimate or time spent
    Confidentiality
    Not confidential
    Not confidential

    You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

    Lock issue
    Unlocked
    0
    0 Participants
    Reference:

    Menu

    Explore Projects Groups Topics Snippets