When Using OS Authenticated Odp.net Connections With Pooling,The Same Connection is Used for Different Users (Doc ID 1085304.1)

Last updated on JUNE 20, 2011

Applies to:

Oracle Data Provider for .NET - Version: 11.1.0.6 to 11.1.0.7 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When using OS Authentication (or kerberos), Oracle client, and ODP version 11.0.7.0 with pooling=true
after user A opens a connection and closes it. Thereby releasing it into the pool, if user B opens another connection using the same connection string. He will obtain the pooled connection and effectively impersonate user A (AUTHENTICATED_IDENTITY is that of user A). This is absolutely unwanted and presents a security flaw.

ODP should create a different connection pool for user B even though the connection string is the same. This means the provider has to differentiate between the connection pools not only upon the actual connection string parameters but to also take into account the identity of the connection string user.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms