IBM WebSphere V5.0 Security - CGISecurity

Figure 10-4 Mapping a group to an Administrative role
10.3.1 CosNaming roles
The J2EE role-based authorization concept has been extended to protect the
WebSphere CosNaming service. CosNaming security offers increased
granularity of security control over CosNaming functions, which affect the content
of the WebSphere Name Space. There are generally two ways in which client
programs will make a CosNaming call. The first is through the JNDI interfaces.
The second is CORBA clients invoking CosNaming methods directly. Four roles
are defined.
Table 10-2 CosNaming roles
Role
Cos Naming Read
Cos Naming Write
Description
Users who have been assigned the
CosNamingRead role will be allowed to
perform queries of the WebSphere Name
Space, such as through the JNDI lookup
method. The special subject Everyone is
the default policy for this role.
Users who have been assigned the
CosNamingWrite role will be allowed to
perform write operations such as JNDI
bind, rebind, or unbind, plus
CosNamingRead operations. The
special-subject, AllAuthenticated, is the
default policy for this role.
242 IBM WebSphere V5.0 Security Handbook