Re: Trusted Connection
From: Steve Townson (steve_townson@descorind.com)
Date: 10/18/02
- Next message: Chris Wood: "Re: Question re: latest SQL 2K security fix"
- Previous message: Mike Stuart: "Question re: latest SQL 2K security fix"
- In reply to: Steve Townson: "Re: Trusted Connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Steve Townson" <steve_townson@descorind.com> Date: Fri, 18 Oct 2002 07:30:33 -0700
Well....
I downloaded the SP2 to the MDAC 2.6, and now it is
prompting me to log in, which is what I want, and when I
log in, I see all the tables that I should ONLY have
permissions for.
HOWEVER, If I check off "Use Trusted Connection", then I
can see and access ALL of the tables, including the tables
I don't have permission to see.
Why is that? How can I use Trusted Connection, but see
all the tables I have permission for? Why do I see ALL of
the tables?
Thanks,
Steve...
>-----Original Message-----
>Thanks Wayne,
>
>HOWEVER, for one of my users, I will create an ODBC DSN
>for my test database ON THEIR COMPUTER, and within this
>database, this particular user only has permissions for
>certain tables.
>
>So, when I set up the ODBC DSN connection for this user,
>when I go into Access, and connect to the database,
>obviously, it is using a Trusted Connection, in which it
>will not ask me for a login and password, but it will
show
>EVERY table in the database and allow this user to add,
>modify, delete, etc, BUT, in SQL Server, this particular
>user does NOT have access to EVERY table.
>
>How can this be? The public group does NOT have access
to
>any Tables at all, so I'm thinking it has something to do
>with how these ODBC DSN and users were originally set up.
>
>The funny thing is.... When I LOG OFF MY COMPUTER, and
>log in as this particular user on my computer, when I go
>into Access and Link a Table, the Trusted Connection WILL
>NOT WORK, and I must log into the database, it WILL
>successfully allow me to see the tables they DO have
>access to.
>
>So, I'm confused as to WHERE I should be looking...
>
>Either the NT Logon or ODBC connection, and I've removed
>the ODBC DSN connection and re-inserted it with this
>particular login name, but no effect.
>
>Thanks,
>Steve...
>
>>-----Original Message-----
>>
>>"Steve Townson" <steve_townson@descorind.com> wrote in
>message
>>news:5c2001c275f8$4958f0e0$3bef2ecf@TKMSFTNGXA10...
>>> Hey all,
>>>
>>> Our SQL Server was set up NOT by me, so I really don't
>>> have a firm grasp of this software.
>>>
>>> The person who originally set this SQL Server up, set
>the
>>> Authentication to: SQL Server and Windows.
>>>
>>> Is this called "Mixed Mode"?
>>
>>Yes this is mixed mode..
>>
>>So, if a user successfully
>>> connects to the server, then when they connect to the
>>> database via. ODBC, then it will automatically connect
>>> them to SQL Server?
>>Users may request a trusted connection or a standard
>connection. Trusted
>>connections require that they be logged on to windows ,
>and that their
>>windows login be a valid sql login... Standard security
>requires they
>>provide a user name and password..
>>>
>>> If I change the Authentication to "Windows Only", will
>SQL
>>> Server prompt the user for a username and password when
>>> trying to connect to the database via. ODBC?
>>SQL never prompts for any of this information... It
would
>be provided by an
>>application or when you are setting up an odbc
connection
>you may store
>>login information with the connection, or provide it 'on
>the fly' in your
>>connection string.
>>
>>>
>>> Currently, when the person set the SQL Server up,
>EVERYONE
>>> has access to ALL tables, so in SQL Server, I GRANTED
>and
>>> REVOKED table access to everyone accordingly, BUT when
I
>>> look at the database via. ODBC, everyone can see EVERY
>>> table still. BUT, if I log off my computer and log on
>as
>>> someone else, then the Trusted connection will not work
>>> and forces a log onto the database. And if I log onto
>the
>>> server using a PC in the plant (they should have NO
>access
>>> and I REVOKED ALL TABLE ACCESS), then they still can
see
>>> all tables, as I assume the Mixed Mode comes in, and it
>>> bypasses all the table permissions for some reason.
>>>
>>> In the end, I want the database to give the appropriate
>>> access to the user logged on, BUT, no matter who is
>logged
>>> on, it bypasses the appropriate table access and gives
>ALL
>>> table access to everyone.
>>>
>>> Any ideas?
>>
>>Take a look at permissions associated with role in your
>database named
>>public... perhaps that is where the extra permissions
are
>being allowed.
>>>
>>> Thanks,
>>> Steve...
>>
>>
>>.
>>
>.
>
- Next message: Chris Wood: "Re: Question re: latest SQL 2K security fix"
- Previous message: Mike Stuart: "Question re: latest SQL 2K security fix"
- In reply to: Steve Townson: "Re: Trusted Connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
