Technical data

8 Protecting System Administration Operations
8-8 Configuring and Managing WebLogic Server
Maintaining a Consistent Security Scheme
The default configuration of groups, roles, server policies, and MBean permissions
work together to create a consistent security scheme. You can, however, make
modifications that limit access in ways that you do not intend.
For example, if you add a user to the Operator role but fail to add the Operator role to
the policy of a server resource, the Operator can call MBean methods that are used in
the startup and shutdown sequence, but cannot use any server-resource operations to
start or stop a server.
To keep MBean security synchronized with the permissions granted by policies,
consider the following when you create or modify a policy:
! Consider always giving the Admin role access to a resource.
! For a policy on a server, consider adding the Operator role.
! For a policy on a deployable resource (such as an EJB, Application, Connector,
or Startup/Shutdown class), consider adding the Deployer role.
In addition, note that if a user does not belong to one of the four groups described in
Table 8-2, the user cannot log in to the Administration Console.
Permissions for Starting and Shutting Down
a WebLogic Server
WebLogic Server enables two techniques for starting and shutting down server
instances, the
weblogic.Server command and the Node Manager. Because the
underlying components for
weblogic.Server and Node Manager are different, the
two commands use different authentication methods.
This section contains the following subsections:
! Permissions for Using the weblogic.Server Command
! Permissions for Using the Node Manager