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

When adding a user to an LDAP connector directory, "active" flag is ignored

XMLWordPrintable

      Symptoms

      When adding a new user to a directory with an LDAP connector, if you specify the user's active flag to false, it will still be created with active flag true. After adding the user, the flag can be turned off without issue.

      This affects the Crowd Admin Console user interface, and also the REST API.

      Steps to Reproduce

      In the admin console, add a user and set the active flag to "false". After the user is added, the active flag is set to true.

      To replicate in REST:

      curl -i -u test:test --data '{ "name" : "my_username", "first-name" : "My", "last-name" : "Username", "display-name" : "My Username", "email" : "user@example.test", "password" : { "value" : "my_password" }, "active" : false }' http://localhost:8095/crowd/rest/usermanagement/1/user --header 'Content-Type: application/json' --header 'Accept: application/json'

      When this command is run, the user is created with the active flag set to "true" despite "false" being the value in the request payload.

      This issue does not affect Crowd internal directories.

      Workaround

      Manually set the flag after the create command, or send a REST command to update the flag.

            [CWD-3018] When adding a user to an LDAP connector directory, "active" flag is ignored

            Ishwinder Kaur added a comment -
            Atlassian Update - 9 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Crowd Data Center, please check our public roadmap.

            Kind regards,
            Crowd Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 9 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Crowd Data Center, please check our public roadmap . Kind regards, Crowd Data Center

              Unassigned Unassigned
              dmason David Mason (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: