Re: webapplication with SQL-server
From: Jeff Cochran (jeff.nospam_at_zina.com)
Date: 07/02/04
- Previous message: Jeff Cochran: "Re: some advice please"
- In reply to: Ludo VdB: "webapplication with SQL-server"
- Next in thread: Bullschmidt: "Re: webapplication with SQL-server"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 02 Jul 2004 20:03:00 GMT
On Fri, 2 Jul 2004 14:22:42 +0200, "Ludo VdB" <ict@vagga.be> wrote:
>I'm new to ASP. Currently I'm planning to develop a web application for my
>company. I want to use ASP for the application and use SQL-server as the
>back-end.
>
>I want to enable a userID and password for every user. I also want to
>specify permissions to parts of the application.
>
>I have 2 scenario's for this:
>
>I let the application handle the permissions to the different parts. I keep
>the permissions in a table in the database so the application knows witch
>user has access to witch part of the application. therefore I will only need
>one connection to the DB.
>
>I let the permissions handle thru the DB. The application passes through
>password and userID to the DB. For every user who logons to the application,
>the application will have a connection to the DB.
>
>What's the best scenario?
>Or witch scenario should I use when?
Neither is best or worst, and assuming you're working with Windows
accounts in the same Windows domain as your app and server, using
Windows authentication might be easier for you to manage. I'd suggest
grouping access levels for convenience, so all users that need access
to part A would be in a group, part B another group, etc.
Jeff
- Previous message: Jeff Cochran: "Re: some advice please"
- In reply to: Ludo VdB: "webapplication with SQL-server"
- Next in thread: Bullschmidt: "Re: webapplication with SQL-server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|