Deprecated: Function set_magic_quotes_runtime() is deprecated in /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php on line 1505 Call Stack: 0.0001 326800 1. {main}() /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:0 0.0003 327652 2. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:25 0.0004 328940 3. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php:20 0.0012 403244 4. vB_Registry->vB_Registry() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php:43 0.0013 403900 5. vB_Input_Cleaner->vB_Input_Cleaner() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php:2337
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /archive/global.php on line 26

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3113

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265
Need help making SQL Server authenticate an AD user [Archive] - MCSE
PDA

View Full Version : Need help making SQL Server authenticate an AD user

Gordon
04-13-04, 06:41 PM
something
I was told to ask in the SQL server for this one.

I have a third party app that is written in Macromedia.
We currently have the users gain access to the database
through a login and password passed to the sql database.
This creates the connection. We then ask the user for
their SS# and D.O.B as a password to enter the
application. This info is stored in tables.

I would like to force SQL server to authenticate the user
using AD and the authentication prompt. We can use the
pass through credential to create the connection, but I
would like the user to be prompted for their domain
userid and password.

In another newsgroup, one of the mvp people suggested
below. I don't understand what he was saying. Can
anyone help clarify this for me and either point me to an
example or tell me how to do this....
:
However, it is probably better for you to simple use SSPI
authentication in
SQL server and just have the user's domain credentials
from their current
logon be used to talk to SQL. SQL can then do the
authentication through
the built-in mechanism


Thanks in advance for the help>>>>
Kevin McDonnell [MSFT]
04-13-04, 06:41 PM
something
To use Integrated Security (NT Authentication) with a client server
application, the user is never prompted for credentials. Meaning,
they are already authenticated on the domain. So, there isn't a way to do
what you're asking.

SQL Security is what you are now using. Which means that as long as the
client can establish a session with the server and supply the right
username and password, for SQL, then they are allowed access to SQL.


Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.
Gordon
04-13-04, 06:41 PM
something
Is there a way to programtically prompt the Integrated
security to come up and check against AD?

Thanks for the help.
Gordon


>-----Original Message-----
>To use Integrated Security (NT Authentication) with a
client server
>application, the user is never prompted for
credentials. Meaning,
>they are already authenticated on the domain. So, there
isn't a way to do
>what you're asking.
>
>SQL Security is what you are now using. Which means
that as long as the
>client can establish a session with the server and
supply the right
>username and password, for SQL, then they are allowed
access to SQL.
>
>
>Thanks,
>
>Kevin McDonnell
>Microsoft Corporation
>
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>
>
>.
>
Kevin McDonnell [MSFT]
04-13-04, 08:13 PM
something
Hi Gordon,
Not from the ODBC or OLEdb API.

There are various authentication API calls that you could implement.
Here's a link to LogonUserex on MSDN.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/se
curity/logonuser.asp

Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.
vBulletin v3.6.2, Copyright ©2000-2010, Jelsoft Enterprises Ltd.