Re: Persist user login info in a Windows form app
From: Joe Kaplan (ilearnedthisthehardway@noway.com)
Date: 03/20/03
- Next message: Gary: "Re: integrated security over vpn"
- Previous message: Joe Kaplan: "Re: Error:Requested registry access is not allowed"
- In reply to: Robert W. Dempsey: "Re: Persist user login info in a Windows form app"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Joe Kaplan" <ilearnedthisthehardway@noway.com> Date: Thu, 20 Mar 2003 11:56:40 -0600
I've never used MySQL, so I am almost certainly not the right person to be
giving you advice on this. I think a lot of this would depend on how you
plan to access the database. If all access is channeled through a single
account (which is the common practice in ASP.NET/SQL 2K applications), then
you would need to pass in the current user to all of your update queries and
then find a way to persist that info and some information about the update
to a log somewhere.
Hopefully you will get some better perspectives on how to accomplish this
from someone else.
Joe K.
"Robert W. Dempsey" <rdempsey@atlanticdominionsolutions.com> wrote in
message news:1c8101c2eee9$3abd2460$a201280a@phx.gbl...
> Joe,
>
> Thank you for your reply. I believe that I want to keep
> it at the database level, as later on we will be giving
> read-only access to outside parties. What do you suggest
> as being the best method to secure the information?
> Also, I am using a MySql database so there are no stored
> procedures. Thank you for your response.
>
> Sincerly,
>
> Robert Dempsey
- Next message: Gary: "Re: integrated security over vpn"
- Previous message: Joe Kaplan: "Re: Error:Requested registry access is not allowed"
- In reply to: Robert W. Dempsey: "Re: Persist user login info in a Windows form app"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
