-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
None
-
3
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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
-
CONFSERVER-46070 Support database connections using LDAP string
- Closed
- relates to
-
JRASERVER-26290 Plugin2 can't access JNDI when using LDAP credentials.
-
- Gathering Impact
-
-
JRACLOUD-41631 Support database connection using LDAP string
- Closed
-
FE-6246 Support database connections using LDAP string
- Not Being Considered
Form Name |
---|
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 now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.
Thanks again.
Regards,
Jira Product Management