Re: spontaneously made login
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 02/19/04
- Next message: Sajith S: "Re: Connection to the server is lost."
- Previous message: Troy: "Access Logs"
- In reply to: rich: "spontaneously made login"
- Next in thread: DB_Princess: "RE: spontaneously made login"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 18 Feb 2004 18:58:37 -0500
Rich,
Don't do that... Create a custom Logins table that you can use to create
these new Logins. These would have nothing to do with SQL Logins but are
just a way to tell Joe from Sue. This Logins table would have an PK that
you use to track their activity. Usually this PK or Login is kept in
session and then you can use it where you need to within the app.
-- Andrew J. Kelly SQL Server MVP "rich" <anonymous@discussions.microsoft.com> wrote in message news:DC48AC0B-0945-40A7-9DBF-8A2BE4E81A4C@microsoft.com... > Has anyone ran into this problem: my company is planning on creating a reservation system on the WWW for classes they hold. The classes will be of two types; classes for emplyees and classes for nonemplyees. The emplyees are going to be easy because all employees have Win2000 logins (active directory) and I can just put these people in a group and drop them into the login page on the Enterprise Manager. Once there they can be given permissions to the tables that hold their class times, ect. > > The nonemployees are the problem. When they hit the web page that faces outside of the enterprise, they do not have Win2000 logins! The only thing I can see to do is what I am calling a spontaneous login. The moment the user goes to the web site, they fill out an application for a login. The web page makes a login that is going to get placed in the active directory. Once in the AD, that new login gets added to the group that is accepted by the SQL Server. The reason for all this control is each person must have the ablity to manager their own class load on line and I have to audit their transactions. The only way to audit in SQL Server tha I can see is that everyone that hits the table must have login that I can pull in from AD.
- Next message: Sajith S: "Re: Connection to the server is lost."
- Previous message: Troy: "Access Logs"
- In reply to: rich: "spontaneously made login"
- Next in thread: DB_Princess: "RE: spontaneously made login"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|