Enabling trusted context for DB2 databases

Enable trusted context in your applications to improve how the application server interacts with DB2® database servers. Use trusted connections to preserve the identity records of clients that are connecting to a DB2 database through your applications; trusted connections can provide a more secure environment by granting access based on the identity of those users.

Before you begin

Ensure that the following prerequisites are met before enabling trusted connections:

About this task

New feature: With trusted connections you can:
  • Access the DB2 database with the caller identity, obviating the need to create a new connection for every user.
  • Preserve the identity of the end-user when the application server is interacting with the database.
  • Strengthen database security by avoiding granting all of the privileges to a single user.
  • Improve performance, as compared to the existing model of using the resetConnection() method to take advantage of identity propagation.
newfeat
Supported configurations: Non-trusted connections cannot be used as trusted connections. If the connection pool contains only non-trusted connections and a request comes in for a trusted connection, a new request will be sent to the database for the trusted connection.sptcfg

Procedure

Enable trusted context for your applications.

What to do next

Be aware of the following error conditions that can occur if trusted context is not configured properly:



In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 12:21:29 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=tdat_trustedcontext
File name: tdat_trustedcontext.html