Community
Participate
Working Groups
When trying to connect to Microsoft SQL Server 2005, using integrated security, the following error message occurs: (Error: This driver is not configured for integrated authentication) Here is my URL: jdbc:sqlserver://gisrv106:1433;databaseName=rlim;integratedSecurity=true I'm using the Microsoft SQL Server 2005 JDBC Driver version 1.1. I have the required DLL (sqljdbc_auth.dll) in the same folder as the eclipse executable. Important note: this problem is intermittent. I've observed 3 different behaviors: 1) Connect without error message; 2) Throw error but connect anyway; 3) Throw error and fail I am able to connect to this server/database consistently using integrated security with other SQL clients, such as Query Analyzer and SQL Management Studio. This problem only occurs when connecting from Eclipse. Brian Fitzpatrick suggested I enter this bug. http://dev.eclipse.org/newslists/news.eclipse.dtp/msg01121.html
I am facing this problem, as well. I have Galileo with the latest DTP. Is there any update on this? (In reply to comment #0) > When trying to connect to Microsoft SQL Server 2005, using integrated > security, the following error message occurs: (Error: This driver is not > configured for integrated authentication) > Here is my URL: > jdbc:sqlserver://gisrv106:1433;databaseName=rlim;integratedSecurity=true > I'm using the Microsoft SQL Server 2005 JDBC Driver version 1.1. I have the > required DLL (sqljdbc_auth.dll) in the same folder as the eclipse executable. > Important note: this problem is intermittent. I've observed 3 different > behaviors: 1) Connect without error message; 2) Throw error but connect > anyway; 3) Throw error and fail > I am able to connect to this server/database consistently using integrated > security with other SQL clients, such as Query Analyzer and SQL Management > Studio. This problem only occurs when connecting from Eclipse. > Brian Fitzpatrick suggested I enter this bug. > http://dev.eclipse.org/newslists/news.eclipse.dtp/msg01121.html
Sorry, but no change I'm afraid. I'm hopeful that someone with more knowledge of SQL Server can take a look and submit a possible patch. This goes way beyond my current knowledge of MSSQL to fix.
I think the "sqljdbc_auth.dll" is needed for this type of connection. So the users either need to copy this file to the system path, for example "c:\Windows\System32" or They can set the "java.library.path" property to the location of the "sqljdbc_auth.dll" file. Refer to "Connecting with Integrated Authentication" section at http://msdn.microsoft.com/en-us/library/ms378428.aspx for more details.
I'm hoping to revive this long dead bug because this should now be possible to resolve this issue with the JDBC 4.0 drivers from Microsoft. https://blogs.msdn.microsoft.com/psssql/2015/01/09/jdbc-this-driver-is-not-configured-for-integrated-authentication/ https://msdn.microsoft.com/en-us/library/gg558122%28v=sql.110%29.aspx The key issue preventing me, as a user, from attempting any of these connection options is that there does not appear to be any way for a user to provide additional connection parameters. This is in contrast to the "Sybase ASE" driver configuration UI (for example), which permit user-defined properties to be specified. With the above links and the ability to create custom properties, one should be able to do Kerberos auth from Linux, Mac and Windows to SQL Server. There are numerous other reasons that it would be beneficial to allow specifying custom properties to be appended to the connection URL. This is because A) the list of valid connection options is immense (https://msdn.microsoft.com/en-us/library/ms378988%28v=sql.110%29.aspx) and B) we actually require some of these to be present for certain databases (e.g. applicationName, which we use essentially as an apikey). After supporting ad hoc properties, more formal support for necessary IWA options such as ServerSPN and authenticationScheme would be nice.
