-
Suggestion
-
Resolution: Won't Fix
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Currently, JIRA is not being able to understand the LDAP connection string in the dbconfig.xml file. eg:
jdbc:oracle:thin:@ldap://myldap:4060/jira00,cn=Oracle,dc=example,dc=com
As a system Administrator, I would like 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.
- is related to
-
CONFCLOUD-46070 Support database connections using LDAP string
- Closed
-
JRASERVER-41631 Support database connection using LDAP string
- Closed
- relates to
-
FE-6246 Support database connections using LDAP string
- Not Being Considered
Form Name |
---|
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!