Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authorizing access to resources

Fine-grained administrative security in heterogeneous and single-server environments

Fine-grained administrative security can be used in heterogeneous or single-server environments with some restrictions.

Fine-grained administrative security in a heterogeneous environment

In WAS v8.0, heterogeneous systems are supported. Specifically, a dmgr node can run in WAS v8.0, some nodes can run WAS v7.0, some nodes can run WAS Version 6.1, and other nodes can run WAS v6.0.

Because the configurations that are done in the dmgr node are always WAS v8.0 or higher configurations, fine-grained administrative security can be enforced when configuring resources that belong to earlier releases. However, run-time code for versions lower than v6.1 cannot enforce fine-grained administrative security. Therefore, any resource instance that is not part of a WAS v6.1 or higher node cannot be added to an authorization group.

Fine-grained administrative security in a heterogeneous environment has the following restrictions:

• Only nodes that are running WAS v8.0 can be part of an administrative authorization group.
• Only servers that are running in a WAS v8.0 node can be part of an administrative authorization group.
• Only applications that are targeted on servers running on WAS v8.0 can be part of an administrative authorization group.

• If a cluster spans nodes of multiple releases, it cannot be part of an administrative authorization group.

• If a cluster spans nodes of multiple releases, none of its members can be part of an administrative authorization group.

• If an application is targeted on a cluster that spans multiple releases, that application cannot be part of an administrative authorization group.

Fine-grained administrative security in a single-server environment

We can also use fine-grained administrative security in a single-server environment. Various applications in the single server can be grouped and placed in different authorization groups. Therefore, different authorization constraints might exist for different applications.

Life cycle of fine-grained administrative resource

An administrative resource that was once part of an authorization group continues to be part of that authorization group until one of the following events occurs:

• The administrative resource is removed from the authorization group. In this instance, the administrative resource belongs to the cell-level authorization group.
• The administrative resource is removed from the configuration. In this instance, the administrative resource does not exist in the configuration, but still exists in the authorization group. Remove this administrative resource from the authorization group.

After the administrative resource is removed from the authorization group, the administrative authorizer runtime must be notified by using the AuthorizationManager refreshAll MBean method.

The refreshAll command must be invoked after AdminConfig.save() and sync nodes. For example:

JACL:

// get AuthorizationGroup Mbean
wsadmin> set agBean [$AdminControl queryNames
type=AuthorizationGroupManager,process=dmgr,*]

wsadmin> $AdminControl invoke &agBean refreshAll

JYTHON:

// get AuthorizationGroup Mbean
wsadmin> set agBean
AdminControl.queryNames('type=AuthorizationGroupManager,process=dmgr,*')

wsadmin> AdminControl.invoke(agBean, 'refreshAll')

The server restart is no longer needed.
Fine-grained administrative security
Role-based authorization

Related

Administrative roles

+

Search Tips   |   Advanced Search