Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-1962

Improve the LDAP stack in JIRA

    XMLWordPrintable

Details

    • 37
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Atlassian Status as of 25/Nov/2010

      Hi Guys,

      We are proud to announce that JIRA 4.3 has just been released!

      4.3 includes the new LDAP integration functionalities that we've been working on.

      In addition, we've completed a whole host of other cool new features. For more information - please check out our release notes at: http://confluence.atlassian.com/display/JIRA/JIRA+4.3+Release+Notes.

      Thanks for your patience, and feel free to contact us if you have feedback or questions for us.

      Regards,
      Edwin Wong
      JIRA Product Management
      edwin at atlassian dot com

      NOTE: We have updated this description based upon our plans to improve the LDAP support in JIRA

      Currently, JIRA's LDAP integration is limited to being able to check a user's password against that in a LDAP directory, as documented at

      http://www.atlassian.com/software/jira/docs/latest/ldap.html

      If you're not aware, Confluence and Bamboo use atlassian-user, FishEye and Crucible have their own stack, and JIRA uses OSUser. Crowd's LDAP stack is different again.

      We are going to put Crowd's LDAP stack into both JIRA and Confluence, and then into the rest of the products. This is a large amount of engineering, and in JIRA in particular, will affect a lot of the code. Much of the Crowd team will be helping out on this effort. The work will not be delivered in JIRA 4.0, but it will start as soon as 4.0 ships. This issue has been assigned to the short term roadmap of JIRA to reflect this.

      Attachments

        1. ldap-syncer.tar.gz
          29 kB
        2. ldap-syncer.tar.gz
          29 kB
        3. ldap-user-importer-1.0.zip
          10 kB

        Issue Links

          has a derivative of

          Suggestion - JRASERVER-23245 Provide a redundant hostname/IP for failover in LDAP

          • Not Being Considered
          incorporates

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-19621 Filters throw exception, if one of the LDAP groups is renamed

          • Low - Low priority issues
          • Closed
          is duplicated by

          Suggestion - JRASERVER-2217 LDAP Integration

          • Closed

          Suggestion - JRASERVER-7867 Active Directory integration (more user info from AD)

          • Closed

          Suggestion - JRASERVER-7868 Active Directory integration (all user info from AD)

          • Closed

          Suggestion - JRASERVER-9700 Ability to query AD/LDAP server and harvest users

          • Closed

          Suggestion - JRASERVER-12638 Support LDAP dynamic groups

          • Closed
          is incorporated by

          Suggestion - JRASERVER-14260 Create Issue from Email Handler - Create Username Flexibility

          • Closed
          is related to

          Suggestion - CONFSERVER-17150 Support nested groups

          • Closed

          Suggestion - JRASERVER-1549 Ability to rename a user

          • Closed

          Suggestion - JRASERVER-3907 LDAP authentication

          • Closed

          Suggestion - JRASERVER-11125 JIRA 4.0 Enterprise Requirements

          • Closed

          Suggestion - JRASERVER-23033 EAP Feedback - LDAP integration

          • Closed

          Suggestion - JRASERVER-24133 Support load-balanced LDAP/AD servers with JIRA

          • Closed

          Suggestion - FE-7017 Support load-balanced LDAP/AD servers with FishEye/ Crucible

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-13325 LDAP against AD will not authenticate when DN includes a ','.

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-13005 LDAP authentication against Active Directory fails if there are escaped double quotes in the user's CN

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-7177 Should allow case insensitive usernames

          • Closed

          Suggestion - JRASERVER-24128 Simpler user filtering for LDAP Directories

          • Closed
          was cloned as

          Suggestion - JRASERVER-24162 Avoid replicating entire LDAP/AD identity directories into JIRA local database

          • Closed

          Activity

            People

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Votes:
              416 Vote for this issue
              Watchers:
              269 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

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