Fusion Middleware Control Help for WebLogic Server

Domain Partition Application Deployment: Administration: Security

Configuration Options     

This page enables you to choose the security identity option used when mapping WebLogic Server user credentials to database user credentials.

Configuration Options

Name	Description
Data Source Name	The name of the JDBC data source.
Set Client ID On Connection	Enables Set Client ID on connection for the data source. When an application requests a database connection, WebLogic Server sets a light-weight client ID on the database connection. By default, it uses the credential mapping to map WebLogic Server user IDs to database user IDs. However, if use-database-credentials is set to true, then the credential mapping is not done and the ID is used directly as a database user ID. It is currently supported for IBM DB2 driver and Oracle thin driver. Support for this feature will be dropped in a future Oracle thin driver release. Oracle recommends using proxy authentication instead of this feature. MBean Attribute (Does not apply to application modules) : JDBCConnectionPoolParamsBean.CredentialMappingEnabled Changes take effect after you redeploy the module or restart the server.
Enable Identity Based Connection Pooling	Enables identity-based-connection-pooling for the data source. When an application requests a database connection, WebLogic Server picks or creates a physical connection with requested DBMS identity based on a map of WebLogic user IDs and database IDs. You must also specify the map of WebLogic Server user IDs to database user IDs (credential mapping). MBean Attribute (Does not apply to application modules) : JDBCConnectionPoolParamsBean.IdentityBasedConnectionPoolingEnabled Changes take effect after you redeploy the module or restart the server.
Oracle Proxy Session	Enables Oracle JDBC Proxy Authentication. Only applicable for the Oracle driver. Requires WebLogic Server user IDs are mapped to database user IDs using credential mapping. MBean Attribute (Does not apply to application modules) : JDBCOracleParamsBean.OracleProxySession Changes take effect after you redeploy the module or restart the server.
Use Database Credentials	If enabled, Oracle database credentials are used in getConnection instead of application server credentials. The database credentials are used to get a proxy session without requiring any work in the credential mapper. MBean Attribute (Does not apply to application modules) : JDBCOracleParamsBean.UseDatabaseCredentials Changes take effect after you redeploy the module or restart the server.