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

FedoraDS in "Configure LDAP User Directory" should be renamed to 389 Directory Server

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • None
    • 1
    • 4
    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Jira Software version: v7.2.6#72008

      Steps to reproduce:

      • In Jira Software, navigate to: Administration -> User management -> User Directories
      • Add Directory -> LDAP
      • In the "Configure LDAP User Directory" page, expand the Directory Type

      Notice that "FedoraDS" is listed as an option. This should be renamed to "389 Directory Server" or "389DS", if there is a character limit. This is because the project was renamed in 2009: http://directory.fedoraproject.org/docs/389ds/FAQ/history.html

            [JRASERVER-63505] FedoraDS in "Configure LDAP User Directory" should be renamed to 389 Directory Server

            Gosia Kowalska added a comment -
            Atlassian Update – 03 October 2019

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 03 October 2019 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management

            sinayion added a comment -

            I was the one that originally put in this request at [GHS-64544|https://support.atlassian.com/servicedesk/customer/portal/20/GHS-64544.]

            Please note, that I was trying this on a Fedora 25 server, with FreeIPA that uses 389DS.
            The newly created user directory was not able to fully pass the tests. It fails the following:

            • Test get user's memberships
            • Test retrieve group
            • Test get group members

            In order to pass the tests fully, I had to choose "Generic Directory Server". Even with the settings being identical, this was the only way to pass the tests.

            sinayion added a comment - I was the one that originally put in this request at [GHS-64544| https://support.atlassian.com/servicedesk/customer/portal/20/GHS-64544 .] Please note, that I was trying this on a Fedora 25 server, with FreeIPA that uses 389DS. The newly created user directory was not able to fully pass the tests. It fails the following: Test get user's memberships Test retrieve group Test get group members In order to pass the tests fully, I had to choose "Generic Directory Server". Even with the settings being identical, this was the only way to pass the tests.

              Unassigned Unassigned
              bmcelveen Branden McElveen (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: