RE: security without using different usernames

Could you maybe use v$session.osuser instead of program? That way you shouldn't even have to rename the exe.

HTH,
-Roy

Roy Pardee
Programmer/Analyst/DBA
SWFPAC Lockheed Martin IT
Extension 8487
-----Original Message-----

From: Ryan [mailto:rgaffuri_at_cox.net]
Sent: Tuesday, July 15, 2003 4:19 PM
To: Multiple recipients of list ORACLE-L Subject: Re: security without using different usernames

yeah i think that might be 'viable'. its a big kludge. but sometimes you have to deal with that.

send out page that alters the name of the executable, so each customer's executable has a different name use program in v$session in a logon trigger to get the customer hit a lookup table to see which schema to use execute immediate to set that up.

thanks.
----- Original Message -----

From: Tanel Poder
To: Multiple recipients of list ORACLE-L Sent: Tuesday, July 15, 2003 7:09 PM
Subject: Re: security without using different usernames

Ryan,

It's alter session set current_schema = name;

Tanel.
----- Original Message -----

From: Ryan
To: Multiple recipients of list ORACLE-L Sent: Wednesday, July 16, 2003 1:29 AM
Subject: security without using different usernames

I know this is terrible design, but the GUI was created by a software engineering group that is seperate from the database group. Its not scalable. So Im trying to come up with a more scalable method. I have no power to change their gui. It rides on the database. I have to live with it. This is not a high enough transaction database to warrant seperate instances.

We have a variety of customers. Each of them has their own versions of data. However, the schema is exactly the same. These tables can get huge, so we dont want to throw them all into the same schema.

Right now, due to the fact that the GUI has a series of logins that are the same across clients, each client has its own instance. This isnt very scalable as we get more business. We have to create another instance and ingest data to it.

Id like to find a way to get all the clients in the same instance with just different schemas and tablespaces. One thing I may have control over would be to slightly rename the executable. If you check v$session, in a client-server application the name of the product connecting to the database is recording. I can handle security based off of that.

My question is what would be the best way? Cant do synonyms for this since its the same login. I think I saw somewhere that there is a session based 'set' command where you can say use this schema. I think it was on asktom and in reference to a question about public synonyms. I cant find it. Anyone know it?

Also is it viable to base a context off of what is in v$sesion with a logon trigger? How would I 'redirect' all queries to a specific schema?

To stress, I cant change the application. Different group with different skillsets. Any suggestions? Received on Tue Jul 15 2003 - 17:33:25 CDT