Title: RE: User access within/outside of app
Here is a trigger that we use to change the optimizer goal at logon based on the operating system account. You would be looking into the value of the v$session.program column instead of the OSUSER used below. Instead of the 'alter session set
One of the ways round this is to have the priv's needed for anything other than
select granted to a role, rather than the generic userid. Make the role
non-default, and require a password to enable it - that way, using the ODBC
connection won't give users any godlike powers.
The issue is how
they won't be able to use that one
anymore.
Jon Walthour
From: Larry Hahn [EMAIL PROTECTED]
Date: 2001/08/21 Tue AM 11:21:04 EDT
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
Subject: User access within/outside of app
List,
We have purchased
Title: RE: User access within/outside of app
What version are you working with?
-Original Message-
From: Larry Hahn [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 21, 2001 11:21 AM
To: Multiple recipients of list ORACLE-L
Subject: User access within/outside of app
List
Tony,
8.1.7 EE on Sun Solaris
Larry
--- Aponte, Tony [EMAIL PROTECTED] wrote:
What version are you working with?
-Original Message-
Sent: Tuesday, August 21, 2001 11:21 AM
To: Multiple recipients of list ORACLE-L
List,
We have purchased a system where users login through
List,
We have purchased a system where users login through
an ODBC connection using a generic Oracle userid. This
userid has full rights to do insert, update, delete,
select on any table in the schema. The app asks for
another username and password which checks the
application security table,
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: User access within/outside of app
List,
We have purchased a system where users login through
an ODBC connection using a generic Oracle userid. This
userid has full rights to do insert, update, delete,
select on any table
List,
We have purchased a system where users login through
an ODBC connection using a generic Oracle userid. This
userid has full rights to do insert, update, delete,
select on any table in the schema. The app asks for
another username and password which checks the
application security table,
within/outside of app
List,
We have purchased a system where users login
through
an ODBC connection using a generic Oracle userid.
This
userid has full rights to do insert, update,
delete,
select on any table in the schema. The app asks
for
another username and password which
recipients of list ORACLE-L
[EMAIL PROTECTED]
Subject: User access within/outside of app
List,
We have purchased a system where users login
through
an ODBC connection using a generic Oracle userid.
This
userid has full rights to do insert, update,
delete,
select on any table
they won't be able to use that one
anymore.
Jon Walthour
From: Larry Hahn [EMAIL PROTECTED]
Date: 2001/08/21 Tue AM 11:21:04 EDT
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
Subject: User access within/outside of app
List,
We have purchased a system
11 matches
Mail list logo