Re: windows authentication & mapping to database
From: Mary Chipman (mchip@nomail.please)
Date: 11/08/02
- Next message: Ben Luckham: "Re: Hosting from a network share."
- Previous message: JJ: "Re: Hosting from a network share"
- In reply to: Vasu: "windows authentication & mapping to database"
- Next in thread: Vasu: "Re: windows authentication & mapping to database"
- Reply: Vasu: "Re: windows authentication & mapping to database"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Mary Chipman <mchip@nomail.please> Date: Fri, 08 Nov 2002 09:43:06 -0500
Assuming you're going to create a primary key or unique index on the
resulting column in the SQL Server table, then you should pick the
narrowest (smallest) possible value that will deliver uniqueness. If
you're connecting to SQLS using the ASPNET account, the Windows
identity information won't be available unless you pass it explicitly
as parameters.
-- Mary
MCW Technologies
http://www.mcwtech.com
On 7 Nov 2002 14:53:45 -0800, vasudev_g@hotmail.com (Vasu) wrote:
>Hi,
>We are developing an ASP.Net web app where users log in thru windows
>authentication. The app has some preferences and data for each user
>stored in sql server 2k.
>Which info do I store about the user in the database to uniquely
>identify him? As far as i know I could store the domain\loginID or
>SID. Could someone tell me which is a better choice or if there are
>any other good alternatives to do this. I looked for pointers on MSDN
>to do this but could not find anything.
>thanks
- Next message: Ben Luckham: "Re: Hosting from a network share."
- Previous message: JJ: "Re: Hosting from a network share"
- In reply to: Vasu: "windows authentication & mapping to database"
- Next in thread: Vasu: "Re: windows authentication & mapping to database"
- Reply: Vasu: "Re: windows authentication & mapping to database"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|