Authentication An Application Using Windows Integrated Authentication

Hi all,

My work is using a shared application
which accesses a MSSQL 2000 database. To access the application, the
folder on the Windows 2003 Server is shared and users can access the
folder through a shared drive.


For the application to access the
database, it uses an ODBC connection to the MSSQL server which
originally used the SA password.


We have recently switched to using
Windows Integrated Authentication because we believe it offers a
higher level of security. However the only way in which we have been
able to enable this is to add the windows users to the SQL server.


The problem with this is that the
application sets permissions for individual users on what records
they can see within the database. We have found that by adding the
windows users to the SQL Server, they can bypass the permissions the
set by the application by simply using any application that can use
an ODBC connection, such as Enterprise Manager, and see all the
database.

One way around this would be to set up
domains of users with access privileges to the tables which reflect
the permissions set by the application, and configuring a view of the
data so they may only see the records that they have permissions to.
However to do this would require a high administrative cost to ensure
that changes made in the application are reflected in the privileges
of the SQL server.

Instead, is there a way the SQL server
can authenticate that the ODBC connection is coming from the correct
application using Windows Integrated Authentication?

This would allow the applcation to
determine security, and stop users from connecting to the SQL server
using other applications.

Alternatively, can the SQL server,
using Windows Integrated Authentication, also ask the application to
supply a username and password?

Any help with this matter would be
greatly appreciated.

Thanks!