Re : Database security

From: James Miller (zrt9_at_cdc.gov)
Date: 06/20/03

  • Next message: James Miller: "SQL Server 2000/Access 2002 security issue" 
    Date: Fri, 20 Jun 2003 07:37:29 -0700

    We have an application that does a similar thing. What we
    did was setup a current access table. Only Admin group
    was granted write priv to this table. When admin program
    started it first checked for a record in the table and
    exited if there was one, meaning someone else was using
    the admin code. If table was empty it attempted to write
    a record to the table, if failed the user is not in the
    admin group. When the user exited the admin code the
    record was deleted. There is a datetime on the record in
    case the admin code closes without deleting the record.

    -Aaron

    >-----Original Message-----
    >I am using SQL Server NT Authentication in an
    application.
    >I have two NT groups 'GroupAdmin' and 'GroupUser' (these
    >names can change and I don't want to hard code them in
    >application). Both these groups access same database but
    >with slightly different grants. I have two applications -
    >Administration and User applications using the same
    >database and NT authentication.
    >
    >a) How can I prevent a 'GroupUser' from accessing the
    >Administration application. Basically, I need to know
    >based on NT Authentication to which group the user
    belongs
    >and what grants the group has on different database
    >objects to validate.
    >b) Only one adminstrator can access 'Administration'
    >application at a time and reject others.
    >I am using 'sp_who' to screen who is accessing the
    >database but I need to know who is in 'GroupAdmin'
    >.
    >

  • Next message: James Miller: "SQL Server 2000/Access 2002 security issue"

    Relevant Pages

    • Re: Sorting out security
      ... > MS Access security. ... > created a new workgroup, added a password for the Admin role, added ... > remote logins to a secured database. ... The location of the current workgroup file is recorded in the ...
      (microsoft.public.access.security)
    • Re: user level security wizard
      ... the name of the database in this shortcut was not the copy, ... But the error message you got I thought was in reference to the mdw file, ... you said that every mdw file has the admin user and the Users Group ... and the security wizard does this for you. ...
      (microsoft.public.access.security)
    • Sorting out security
      ... MS Access security. ... created a new workgroup, added a password for the Admin role, added groups, ... user IDs and passwords for users and allocated permissions on the ... remote logins to a secured database. ...
      (microsoft.public.access.security)
    • Re: Help - Pathworks & Windows 2000 Advanced Server
      ... Your privilege level on domain TURPINS-WM is ADMIN. ... The partial synchronization replication of the LSA database from the ...
      (comp.os.vms)
    • Re: Problems setting up access security
      ... The Admin user still owns the database object. ... You secured it using the system.mdw, thinking that you were using your secure mdw. ...
      (microsoft.public.access.security)