Hi Paul, I don't think we are hard coding trusted_connection in the MSSQL connection strings. The UID and PWD is also accepted in the ODBC connection strings according to: https://msdn.microsoft.com/en-us/library/ms130822.aspx
Best regards, Tamas 2015-12-28 22:05 GMT+01:00 Paul Meems <[email protected]>: > I'm trying to connect to a MSSQL database on Azure using a SQL Server user > account but I get this from GDAL (v2): Unable to initialize connection to > the server for MSSQL:server=***;database=***;user=*** ;password=*** [SQL > Server]Login failed. The login is from an untrusted domain and cannot be > used with Windows authentication. > > A co-worker looked at the code of the MSSQL driver and noticed you > are using the ODBC drivers, but are hard coding the trusted_connection > parameter to be yes. > Is this by design? > Should I file a issue report? > > Thanks, > > Paul > > *Paul Meems * > Release manager, configuration manager > and forum moderator of MapWindow GIS. > www.mapwindow.org > > Owner of MapWindow.nl - Support for > Dutch speaking users. > www.mapwindow.nl > > > Download the latest MapWinGIS mapping engine. > <https://mapwingis.codeplex.com/releases> > > Download the latest MapWindow 5 open source desktop application. > <https://mapwindow5.codeplex.com/releases> > > _______________________________________________ > gdal-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
