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

User should exist in the local directory after successful authentication

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.2, 2.2 Iteration 5
    • 2.2 Iteration 4
    • Embedded
    • None

      Scenario: JIRA -> Crowd -> LDAP Delegated Auth

      1. New user is created in LDAP.
      2. New user tries to log in in JIRA.

      -> Authentication succeeds, and the new user is created in Crowd, but will not be visible in JIRA before the next synchronisation with Crowd.

      The specific problem is that DBCachingRemoteDirectory#authenticate does not create non-existing users in the local directory.

      Ideally we would do full synchronisation in this case, but a full synchronisation can take a very long time. Creating user in the local directory and adding group memberships for the user should fix this situation.

            [CWD-2238] User should exist in the local directory after successful authentication

            Stephan Haslinger added a comment -

            I am able to reproduce this. Should I contact support?

            Stephan Haslinger added a comment - I am able to reproduce this. Should I contact support?

            joe added a comment - - edited

            This works for me. I tested with Confluence 3.5.9, Crowd 2.3.2.

            I created a delegated directory in Crowd with a confluence-users group set as default membership. I configured Confluence to use Crowd as a remote directory. I synchronised, so Confluence knew about the confluence-users group in the delegated directory. Then, after creating new users in LDAP, I logged in to Confluence as those users. The user log in was accepted and Confluence saw them as members of confluence-users.

            joe added a comment - - edited This works for me. I tested with Confluence 3.5.9, Crowd 2.3.2. I created a delegated directory in Crowd with a confluence-users group set as default membership. I configured Confluence to use Crowd as a remote directory. I synchronised, so Confluence knew about the confluence-users group in the delegated directory. Then, after creating new users in LDAP, I logged in to Confluence as those users. The user log in was accepted and Confluence saw them as members of confluence-users .

            Stephan Haslinger added a comment -

            I'm still running into that problem with Confluence 3.5.9 + Crowd Version: 2.3.2 (Build:#524 - 10-08-2011)

            Stephan Haslinger added a comment - I'm still running into that problem with Confluence 3.5.9 + Crowd Version: 2.3.2 (Build:#524 - 10-08-2011)

              onevalainen Olli Nevalainen
              onevalainen Olli Nevalainen
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 6h Original Estimate - 6h
                  6h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 8.1h
                  8.1h