I have just set up a small database (SQL 2000/ADP/Windows XP) and created
three logins (the system uses Windows authentication).
I was surprised that when logging in from a different machine under a
different userID (i.e. one that doesn't have an account on the database
etc.) I was still able to browse and edit data.
My question then is... What do I need to do to make sure access is
restricted purely to users listed again the database?
SourceForge.net Sitewide Update: Jan 26th, 2005 (fwd) ... I just returned from an enjoyable Open Source conference in Hawaii ... open sourced the database under the name Derby. ... The CVS client SF.net staff recommend for MS Windows users is ...priority technical support.... (comp.os.linux.announce)
Re: Windows Authentification against a list of users ... > One thing you might do would be to validate against a group in the domain ... > as your list of allowed users instead of your database though. ... > using Forms authentication instead of Windows authentication and creating ... That would allow you to combine Windows... (microsoft.public.dotnet.security)
Re: Sql Server Login ... firstly I was under the impression SQL authenticaiton will be better ... But now I know windows authentication is recommended. ... Now my application is ready and talking to this database in MSDE. ... (microsoft.public.sqlserver.msde)
Re: Authenticating domain users ... Is it a Web Application or a Windows...network authentication based upon the model used. ... and now I want to access the database.... > password be set to the the user's domain username and password? ... (microsoft.public.dotnet.languages.csharp)
Re: Is this possible?? ... I understand Windows security but since I've not seen A2007 live, ... The backend is on the server in it's own file. ...database, but everyone does not need to have access to tblwage which is ... (microsoft.public.access.tablesdbdesign)
