Skip Headers

# Configuring Oracle Database Proxy Authentication

Previous

Next

You can configure a database login to use Oracle Database proxy authentication with an Oracle Database platform in JSE applications and JEE applications using OC4J native or managed data sources with Oracle JDBC driver release 10.1.0.2.0 or later and external connection pools only.

There is no TopLink Workbench support for this feature. To configure TopLink to use Oracle Database proxy authentication, you must use Java (see "Using Java").

For more information, see "Oracle Database Proxy Authentication".

You can use TopLink support for Oracle Database proxy authentication by doing the following:

- Providing Authenticated Reads and Writes of Secured Data Through the Use of an Exclusive Isolated Client Session

- Providing Authenticated Writes for Database Auditing Purposes With a Client Session

- Providing Authenticated Writes for Database Auditing Purposes With a Client Session

Providing Authenticated Reads and Writes of Secured Data Through the Use of an Exclusive Isolated Client Session

In this configuration, the client Session is an isolated client session (see "Isolated Client Sessions") that uses an exclusive proxy connection. You must acquire the client session using a `ConnectionPolicy` that specifies the proxy authentication user credentials.Reads and writes of secured data are performed through the proxy-authenticated connection. Reads of nonsecured data occur through nonproxy-authenticated connections.

If you are using Oracle Private Virtual Database (VPD) (see "Isolated Client Sessions and Oracle Virtual Private Database (VPD)"), use this configuration to set up VPD support entirely in the database. That is, rather than making the isolated client session execute SQL (see "PostAcquireExclusiveConnection Event Handler" and "PreReleaseExclusiveConnection Event Handler"), the database performs the required set up in an after login trigger using the proxy `session_user`.

Providing Authenticated Writes for Database Auditing Purposes With a Client Session

In this configuration, isolated data or exclusive connections are not required. You must acquire client session using a ConnectionPolicy that specifies the proxy authentication user credentials.

Writes are performed through the proxy-authenticated connection. Reads occur through nonproxy-authenticated connections. This enables the database auditing process to access the user that performed the write operations.

Providing Authenticated Reads and Writes With a Database Session

In this configuration, you use a `DatabaseSession` object with a proxy-authenticated login. All reads and writes occur through the proxy-authenticated connection.

Note: Oracle recommends that you exclusively use server and client sessions in a three-tier environment. Do not use database sessions in a three-tier environment. Ensure that a database session is used by a single user and not accessed concurrently.