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

Fine-grained administrative security in a heterogeneous environment has the following restrictions:
  • Only nodes that are running WebSphere® Application Server Version 8.0 can be part of an administrative authorization group.
  • Only servers that are running in a WebSphere Application Server Version 8.0 node can be part of an administrative authorization group.
  • Only applications that are targeted on servers running on WebSphere Application Server Version 8.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

You 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.




Related concepts
Fine-grained administrative security
Role-based authorization
Related reference
Administrative roles
Concept topic Concept topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 5:16:49 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-base-iseries&topic=csec_finehet_admsec
File name: csec_finehet_admsec.html