Ordinarily, SQL Relay logs into the database as a particular user several times and hands those sessions off to SQL Relay clients, thus avoiding the cost of connecting to and disconnecting from the database over and over. A sometimes undesirable side-effect of this approach is that it is impossible to distinguish which queries were run by which SQL Relay users from within the database since SQL Relay uses the same database user to run all queries.

Oracle n-tiered authentication provides a way around this side-effect.

If you set up a proxy role, a proxy user and a set of users that can be proxied by that proxy user in Oracle and configure SQL Relay to use the "database" authentication tier, SQL Relay users will map to Oracle users.

First, make sure your database's compatibility mode is set to a version equal to or higher than "8.1.0". Log in as the sys user and run:

select name,value from v$parameter where name='compatible'

(Note: In 8i, you can log in as sys using sqlplus sys/syspass where syspass is replaced with the sys user's password. In 9i/10g, you must use sqlplus sys/syspass as sysdba to log in as the sys user.)

If the compatibility mode is not 8.1.0 or greater, then follow these steps:

If you have an $ORACLE_HOME/dbs/init$ORACLE_SID.ora file, change the "compatible" parameter to a version equal to or higher than "8.1.0".

If you have an $ORACLE_HOME/dbs/spfile$ORACLE_SID.ora then you can log in as the sys user and run:

ALTER SYSTEM SET compatible='8.1.0' SCOPE=spfile

(Note: In 8i, you can log in as sys using sqlplus sys/syspass where syspass is replaced with the sys user's password. In 9i/10g, you must use sqlplus sys/syspass as sysdba to log in as the sys user.)

After changing the compatibility mode, restart the database.

Next, log into the database as system and create a set of users:

CREATE USER user1 IDENTIFIED BY user1;
GRANT CREATE SESSION TO user1;
CREATE USER user2 IDENTIFIED BY user2;
GRANT CREATE SESSION TO user2;
CREATE USER user3 IDENTIFIED BY user3;
GRANT CREATE SESSION TO user3;

You may also need to run:

ALTER USER user1 QUOTA UNLIMITED ON tablespace_name;
ALTER USER user2 QUOTA UNLIMITED ON tablespace_name;
ALTER USER user3 QUOTA UNLIMITED ON tablespace_name;

Where tablespace_name is replaced with the name of the tablespace that the user's schema was created in. This appears to be necessary with Oracle 10g, but I don't remember it being necessary prior to 10g.

Now, create a proxy role and give the users access to it:

CREATE ROLE proxyrole;
GRANT proxyrole TO user1;
GRANT proxyrole TO user2;
GRANT proxyrole TO user3;

At this point, you'll need to perform grants to the proxyrole to give it whatever permissions that the users that may use it will need. Grants to roles are the performed like grants to users. For example if proxyrole needs random access to "publictable" and read access to "readonlytable":

GRANT all ON publictable TO proxyrole;
GRANT select ON readonlytable TO proxyrole;

Create a proxy user:

CREATE USER proxyuser IDENTIFIED BY proxyuser;
GRANT CREATE SESSION TO proxyuser;

Give the users access through the proxy user:

ALTER USER user1 GRANT CONNECT THROUGH proxyuser WITH ROLES proxyrole;
ALTER USER user2 GRANT CONNECT THROUGH proxyuser WITH ROLES proxyrole;
ALTER USER user3 GRANT CONNECT THROUGH proxyuser WITH ROLES proxyrole;

Note that you cannot do this with the SYSTEM user. Ie. you cannot run:

ALTER USER SYSTEM GRANT CONNECT THROUGH proxyuser WITH ROLES proxyrole;

If you need to access the database through SQL Relay as the SYSTEM user, you must set up an instance of SQL Relay which logs in as the SYSTEM user and use that instance for accessing the database.

If auditing is enabled in your database, you can enable auditing of the queries that the users have run through the proxyrole as follows:

AUDIT SELECT ANY TABLE BY proxyuser ON BEHALF OF user1;
AUDIT SELECT ANY TABLE BY proxyuser ON BEHALF OF user2;
AUDIT SELECT ANY TABLE BY proxyuser ON BEHALF OF user3;

Queries will show up in the audit table as having been run by user1, user2 or user3, rather than as the proxyuser.

SQL Relay should be set up to use the database authentication tier and to log into Oracle as the proxy user. Below is an sqlrelay.conf file that does this. Note the authtier attribute of the instance tag. Note also that there are no users defined as they are unnecessary for this kind of configuration.

<?xml version="1.0"?>
<!DOCTYPE instances SYSTEM "sqlrelay.dtd">
<instances>

        <instance id="proxyuser" port="9000" socket="/tmp/proxyuser.socket" dbase="oracle8" connections="1" maxconnections="3" maxqueuelength="0" growby="1" ttl="60" endofsession="commit" sessiontimeout="600" runasuser="nobody" runasgroup="nobody" cursors="5" authtier="database">
                <users>
                </users>
                <connections>
                        <connection connectionid="proxyuser" string="user=proxyuser;password=proxyuser;oracle_sid=ora1;" metric="1"/>
                </connections>
        </instance>

</instances>

Now that Oracle and SQL Relay are configured, you can run SQL Relay as follows:

sqlr-start -id proxyuser

You can use sqlrsh to access it as any of the database level users that you created earlier:

sqlrsh localhost 9000 "/tmp/proxyuser.socket" user1 user1
or
sqlrsh localhost 9000 "/tmp/proxyuser.socket" user2 user2
or
sqlrsh localhost 9000 "/tmp/proxyuser.socket" user3 user3