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

Crowd Integration Cache for JIRA is not updated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Medium Medium
    • None
    • 2.0, 2.0.1, 2.0.2, 2.0.3
    • None

      When the User does not exist in the Delegated Directory and Crowd finds him in LDAP, the user is correctly added to Crowd's DB, however, the JIRA App Cache is not Updated.

      Possible consequences:

      1. The user can login, but will not be a member of the jira-users group
      2. Sometimes the user can't login


      Steps to Reproduce:

      1. Delete the test user from Crowd delegatedDirectory. The directory is configured to automatically add jira-users group membership on new user creation in the local group memberships directory.
      2. Restart Crowd, JIRA, and start up Confluence. We log into JIRA as an administrator account, and view the user browser. The test user is not present. Log out of the administrator account, and then log in with the test user.
      3. The test user authenticates, but does not gain group membership of jira-users. The user does belong to confluence-users, however.
      4. The test user then authenticates to Confluence. This is successful, and the user belongs to both jira-users and confluence-users.
      5. The test user logs out of JIRA, and back into JIRA, but still does not have jira-users membership. Verifying in Crowd, the user now exists and owns both jira-users and confluence-users.
      6. After restarting JIRA, the test user can now log into JIRA, and has membership of both groups.

            [CWD-1796] Crowd Integration Cache for JIRA is not updated

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 - restricted [ 1510937 ] New: JAC Bug Workflow v3 [ 3365532 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1392433 ] New: Simplified Crowd Development Workflow v2 - restricted [ 1510937 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 273558 ] New: Simplified Crowd Development Workflow v2 [ 1392433 ]
            joe made changes -
            Resolution New: Cannot Reproduce [ 5 ]
            Status Original: Needs Verification [ 10004 ] New: Resolved [ 5 ]
            Diego Berrueta made changes -
            Remote Link New: This issue links to "Wiki Page (Extranet)" [ 25947 ]

            Diego Berrueta added a comment - - edited

            I've tried to reproduce the issue with Crowd 2.5.2, Jira 5.1.4 and Confluence 4.3, without success. This is the setup I've used:

            1. I've configured a delegated OpenLDAP directory in Crowd.
            2. Groups 'jira-users' and 'confluence-users' have been created in the delegated directory in Crowd.
            3. The directory has been configured in Crowd to automatically add users to these two groups after a successful login.
            4. A remote Crowd directory has been configured in Jira and Confluence, making sure it has been configured for incremental synchronisation. Directory synchronisation has been tested successfully.
            5. Products have been restarted as described in the original report.
            6. To make sure there is no previous trace of the user in any of the directories/caches, a new user has been created directly in the LDAP directory, i.e., without using Crowd. It has been verified that the user does not appear in Crowd, Jira or Confluence.
            7. When the user authenticates in Jira or Confluence, the user is automatically created in the delegated directory and added to both groups (checked using Crowd), and is also created in Jira/Confluence and added to both groups (checked using the admin console of Jira/Confluence).

            We would be interested to know if this issue is still affecting users of older versions of the products.

            Diego Berrueta added a comment - - edited I've tried to reproduce the issue with Crowd 2.5.2, Jira 5.1.4 and Confluence 4.3, without success. This is the setup I've used: I've configured a delegated OpenLDAP directory in Crowd. Groups 'jira-users' and 'confluence-users' have been created in the delegated directory in Crowd. The directory has been configured in Crowd to automatically add users to these two groups after a successful login. A remote Crowd directory has been configured in Jira and Confluence, making sure it has been configured for incremental synchronisation. Directory synchronisation has been tested successfully. Products have been restarted as described in the original report. To make sure there is no previous trace of the user in any of the directories/caches, a new user has been created directly in the LDAP directory, i.e., without using Crowd. It has been verified that the user does not appear in Crowd, Jira or Confluence. When the user authenticates in Jira or Confluence, the user is automatically created in the delegated directory and added to both groups (checked using Crowd), and is also created in Jira/Confluence and added to both groups (checked using the admin console of Jira/Confluence). We would be interested to know if this issue is still affecting users of older versions of the products.
            Diego Berrueta made changes -
            Status Original: Open [ 1 ] New: Needs Verification [ 10004 ]
            Diego Berrueta made changes -
            Link New: This issue relates to CWD-2956 [ CWD-2956 ]
            joe made changes -
            Remaining Estimate New: 40h [ 144000 ]
            Original Estimate New: 40h [ 144000 ]
            shihab made changes -
            Labels New: bug-fix

              Unassigned Unassigned
              rbattaglin Renan Battaglin
              Affected customers:
              10 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved:

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