Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-7063

Unable to edit "Crucible user" setting for externally managed users

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Low
    • Resolution: Fixed
    • 3.6.1, 3.6.2, 3.8.1, 3.9.0
    • 4.0.0
    • None

    Description

      Summary

      In FishEye/Crucible, if a user is managed externally (i.e. JIRA/Crowd/LDAP), and local editing of email address and display name is disabled, it is not possible to enable or disable Crucible access for that user.

      Steps to Reproduce

      1. Integrate Crucible with JIRA for user management.
        • For When synchronisation happens set Copy new users and changes to existing users (local editing of email address and display name is disabled).
      2. Synchronize the users.
      3. Within Crucible edit a user, uncheck the box Crucible user and click in Apply. It will fail because the user is managed externally so no changes can be applied. See screenshot below

      Expected Results

      Crucible access for the user should be editable, as this is not managed externally.

      Actual Results

      Crucible access cannot be edited if the user is managed externally, and local editing of email address and display name is disabled.

      Workaround 1 - Bulk Edit

      1. Under Administration >> User Settings >> Users select the checkbox for the users that you would like to enable/disable Crucible for
      2. At the bottom of the page, select "Enable Crucible" or "Disable Crucible" in the Bulk actions dropdown menu and select "GO"

      Workaround 2

      1. Go to Crucible Administration > Authentication > JIRA/Crowd Authentication, edit its setting and set When synchronisation happens to Copy only new users (local editing of email address and display name is enabled) temporarily. Proceed with the groups configuration and Save.
      2. Within Crucible edit the user, checking/unchecking the Crucible user box. It will work now as for now it is possible to edit users locally.
      3. Go back to Crucible Administration > Authentication > JIRA/Crowd Authentication and edit the settings to set When synchronisation happens back to the previous setting.

      Workaround 3 - REST API

      An example of how you could enable a user for Crucible access is as follows:

      curl -u <ADMIN USER> -v -X PUT -d "{\"crucible\":true}" -H "Content-Type: application/json" <URL>:<PORT>/rest-service-fecru/admin/users/<USERNAME>
      

      Attachments

        Issue Links

          Activity

            People

              dlahn David Lahn (Inactive)
              grefosco Gustavo Refosco (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 0.8h
                  0.8h