Page 1 of 1

Integrated Security in SQL Server

Posted: Thu 29 Nov 2007 09:45
by Jos
Hi,

How can I set the connection parameters for the SQL Server connection so that it has Integrated Security? I tried to add a parameter 'Integrated Security=SSPI', but this doesn't seem to work.

Kind regards,
Jos.

Posted: Thu 29 Nov 2007 12:50
by Antaeus
To enable Integrated Security, you should change the Authentication property of TMSConnection to auWindows. This is an easier way than changing the connection string.
If this does not help you to solve the problem you have encountered, please describe what behaviour do you except, and what is the real behaviour of SDAC.

Posted: Thu 29 Nov 2007 14:30
by Jos
Antaeus,

I can't set Integrated Security on de TSQLConnection component. That is the component in de dbExpress driver edition, right? You are referring to the SDAC, a separate componentsuite from Core Lab.

Jos.

Posted: Thu 29 Nov 2007 16:14
by Antaeus
The Integrated Security connection setting is not supported in DbxSda. DbxSda supports only following connection string options:
  • Application Name
  • AutoTranslate
  • Failover Partner
  • Language
  • MARS Connection
  • Network Library
  • PacketSize
  • Use Encryption for Data
  • Workstation ID
Integrated Security is supported only in SDAC.

Posted: Thu 29 Nov 2007 20:59
by Jos
Antaeus,

Sorry to hear about this now. We purchased the dbExpress driver about 2 weeks ago. Our client for which we develop an application requires us to use Integrated Security. It is BTW the preferred way of authentication in SQL Server according to Microsoft.
Is there a change that integrated security is coming soon in the dbExpress driver?
If not, then dbExpress is not of use to us. Would you consider a refund?

Kind regards,
Jos.

Posted: Fri 30 Nov 2007 07:38
by Antaeus
To connect to SQL Sever using the Integrated Security authentication, you just need to erase the User_Name parameter.

Posted: Mon 03 Dec 2007 08:17
by Jos
This works.
Thanks.