Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
21
-
Description
Hi everyone,
Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Server.
We spend a significant amount of time on an ongoing basis to determine our product investments in Bitbucket Server. Unfortunately, we are not currently planning to address this suggestion in the next 12 months. In the last 12 months, we've resolved 10 of the top 30 feature requests, and our upcoming roadmap includes a number of other top voted suggestions, including in-browser editing, improvements to search functionality, better JIRA integration, and providing an even better code review experience.
I understand that this may be disappointing, but we believe it’s important for us to be open, honest and transparent with our customers. Product feedback is collected from a number of different sources and is evaluated when planning the product roadmap. You can learn more about our process here.
Norman Ma
Product Manager - Bitbucket Server
With the move from using jTDS to access Microsoft SQL Server in Stash to using Microsoft's own JDBC driver, a nice improvement to also make would be to allow selecting integrated authentication in the UI.
Currently, to use integrated authentication users must directly modify stash-config.properties to set their own jdbc.url value. This means it is not possible to migrate to SQL Server using integrated authentication, nor is it possible to select SQL Server during initial setup if integrated authentication is required.
When SQL Server is selected as the database, a checkbox for selecting integrated authentication could be added. When selected, the username and password prompts should be disabled/hidden and no longer considered required; any credentials provided in those fields will be ignored.
When integrated authentication is selected, the server should choose the correct sqljdbc_auth.dll for the JVM's architecture and include it in the java.library.path automatically. Currently, this step must be done manually, in addition to modifying the JDBC URL.
Attachments
Issue Links
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-