Date: Fri, 23 Jul 2004 11:41:57 +0100
A system that is being designed will use ActiveDirectory to store
userinformation for a SQL Server 200 base web app. It was decided that only
the windows account username need be stored in the database for
authentication by the web app.
However I realised that if we chould take this route everytime I wish to
display a users name I will have to do a lookup to get the details from the
to AD after getting the windwos user account from SQL Server.
This sounds rubbish to be frank. Should I just store what I need i.e.,
First name, surname, email address in the database and us the AD purely for
authentication. But then doesn't this loose some of the valu eof the AD and
means there are two sources of info to maintain.
Does anyone have any metrics on connection/transaction time with an AD, if
it is nominal then I will go with the original plan.
Also any advice on the topic would be greatly appreciated.
P.S. ASP.NET 1.1, C#, SQL SERVER 2000, WindowsServer 2003
- Re: windows authentication & mapping to database
... resulting column in the SQL Server table, ... you're connecting to SQLS using the ASPNET account, the Windows ... >We are developing an ASP.Net web app where users log in thru windows ... >Which info do I store about the user in the database to uniquely ...
- Re: Newbie help
... think I can probably get what I need using SQL Server (the ... > To efficiently store and retrieve data for your needs, ... You only store changed values (as ...
- Re: meta data & full text search
... There are more issues (transaction control, change control, audit of ... storing the files in a SQL Server table's column defined with an IMAGE ... if you store the files ... consistency of the database, indices, backup, restore, etc. ...
- audit tables, delete triggers and sql server authentication
... i have a web app connecting to a sql server using sql server ... the web app however, is using windows authentication. ... i have an updatedby and an updatedate. ... how can the trigger know ...
- Re: Web app on a web server, but run on localhost
... You have to know where your web app runs, ... As for the database setup error, it is because you are using SQL Server2005/Express as ASP.NET website's management data store, such as membershipmanagement. ... In this case, the data file used by SQL Server/Express must be on the computer where SQL Server/Express installs, i.e. must be on local drive, not on network location. ...