Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-4311

Unable to manage user status locally LDAP: error code 50 - 00002098

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.12.0
    • 2.6, 2.7.2, 2.8
    • None

      Steps to reproduce:

      1. Create a LDAP directory with read and write permission
      2. Turn on manage user Locally option
      3. Deactivate any user from the directory

      Expected Result
      The user has been deactivated without error, and the change is not propagated to the backing directory. See https://confluence.atlassian.com/display/CROWD/Deleting+or+Deactivating+a+User.

      End result:
      Error message :

      org.springframework.ldap.NoPermissionException: [LDAP: error code 50 - 00002098: SecErr: DSID-03150BB9, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0]; nested exception is javax.naming.NoPermissionException: [LDAP: error code 50 - 00002098: SecErr: DSID-03150BB9, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0]; remaining name 'SOME USER DN'
      

      Cause:
      I suspect this issue was caused by the Configured Bind DN user have insufficient permission to write on AD, as when you click on update, it will prompt to check user's detail as below:

      Managing user locally should not update anything to the LDAP/AD

        1. crowd.png
          crowd.png
          33 kB
        2. unnamed.png
          unnamed.png
          48 kB

            [CWD-4311] Unable to manage user status locally LDAP: error code 50 - 00002098

            As workaround it's possible to manage the user's statuses locally by direct update the database.
            Modifications are kept and immediately diffused to all clients connected to Crowd.

            UPDATE cwd_user SET active='F' WHERE username='someusername'
            

            NB: Only the column 'active' has been tested with Crowd 2.7.2

            Pascal CORBISIER added a comment - As workaround it's possible to manage the user's statuses locally by direct update the database. Modifications are kept and immediately diffused to all clients connected to Crowd. UPDATE cwd_user SET active='F' WHERE username='someusername' NB: Only the column 'active' has been tested with Crowd 2.7.2

            Hi,

            This error is very disabling if company policy does not allow for changes in the directory.
            Can you plan this issue for the next release please.

            Pascal CORBISIER added a comment - Hi, This error is very disabling if company policy does not allow for changes in the directory. Can you plan this issue for the next release please.

            joe added a comment -

            Yes, I believe the problem here is that Crowd attempts to set all fields, rather than just storing the status locally. Examining the rest of the exception would confirm that, and show specifically what's failing to be set.

            Although I appreciate that this is a major problem in this deployment, I've reduced the priority from 'critical' as this isn't a regression or production issue for an existing installation.

            joe added a comment - Yes, I believe the problem here is that Crowd attempts to set all fields, rather than just storing the status locally. Examining the rest of the exception would confirm that, and show specifically what's failing to be set. Although I appreciate that this is a major problem in this deployment, I've reduced the priority from 'critical' as this isn't a regression or production issue for an existing installation.

            If the user Bind DN have not write permission, user's statuses cannot be edited.
            If I edit the user, an error occurs:

            Whereas no action should be made on to the remote directory.

            Pascal CORBISIER added a comment - If the user Bind DN have not write permission, user's statuses cannot be edited. If I edit the user, an error occurs: Whereas no action should be made on to the remote directory.

              ppetrowski Patryk
              wwong Wayne Wong
              Affected customers:
              9 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: