Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-6246

Support database connections using LDAP string

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Allow configuring the database setting to use Oracle Internet Directory (using LDAP connection string) so that the instance can find its way to the database hostname via Oracle Internet Directory. Connection string example:

      jdbc:oracle:thin:@ldap://myldap:4060/fecru00,cn=Oracle,dc=example,dc=com

      That way customers don't have to hardcode the database hostname. As system administrators, customers may want to use the LDAP string, so that the true server name aren't in the string so if they change something, no application changes would need to be made.

            [FE-6246] Support database connections using LDAP string

            Marek Parfianowicz added a comment -
            Atlassian Update – 4 February 2019

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Regards
            Marek Parfianowicz
            Fisheye/Crucible TL

            Marek Parfianowicz added a comment - Atlassian Update – 4 February 2019 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it. Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Regards Marek Parfianowicz Fisheye/Crucible TL

            Piotr Swiecicki added a comment -

            Seems like OID is supported by thin driver, so there is a chance it works out of the box,s ee http://www.oracle.com/technetwork/topics/jdbc-faq-090281.html#05_16
            This needs to be verified though

            Piotr Swiecicki added a comment - Seems like OID is supported by thin driver, so there is a chance it works out of the box,s ee http://www.oracle.com/technetwork/topics/jdbc-faq-090281.html#05_16 This needs to be verified though

              Unassigned Unassigned
              fkraemer Felipe Kraemer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: