The following sections provide information on how WebLogic Server uses roles and policies to secure JDBC data sources:
You can optionally restrict access to JDBC data sources. In WebLogic Server, security policies answer the question "who has access" to a WebLogic resource. A security policy is created when you define an association between a WebLogic resource and a user, group, or role. A WebLogic resource has no protection until you assign it a security policy. For instructions on how to set up security for all WebLogic Server resources, see "Use roles and policies to secure resources" in Oracle WebLogic Server Administration Console Help. For more information about securing server resources, see Securing Resources Using Roles and Policies for Oracle WebLogic Server.
You can protect JDBC resource operations by assigning Administrator methods which can limit the actions that an administrator may take upon a JDBC data source. See "Java DataBase Connectivity (JDBC) Resources" in Securing Resources Using Roles and Policies for Oracle WebLogic Server.
JDBC MBeans allow only the Admin and Deployer roles. The following sections provide information on the security roles defined for JDBC MBeans:
See "Default Security Policies for MBeans" in Oracle WebLogic Server MBean Reference for information on default security settings for WebLogic Server.
The following domain configuration JDBC MBeans that have settings that override the default security settings.
See "Domain Configuration MBeans" in Oracle WebLogic Server MBean Reference.
The following system module JDBC MBeans that have settings that override the default security settings.
See "System Module MBeans" in Oracle WebLogic Server MBean Reference.