13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 10-4 Mapping a group to an Administrative role10.3.1 CosNaming rolesThe J2EE role-based authorization concept has been extended to protect the<strong>WebSphere</strong> CosNaming service. CosNaming security offers increasedgranularity of security control over CosNaming functions, which affect the contentof the <strong>WebSphere</strong> Name Space. There are generally two ways in which clientprograms will make a CosNaming call. The first is through the JNDI interfaces.The second is CORBA clients invoking CosNaming methods directly. Four rolesare defined.Table 10-2 CosNaming rolesRoleCos Naming ReadCos Naming WriteDescriptionUsers who have been assigned theCosNamingRead role will be allowed toperform queries of the <strong>WebSphere</strong> NameSpace, such as through the JNDI lookupmethod. The special subject Everyone isthe default policy for this role.Users who have been assigned theCosNamingWrite role will be allowed toperform write operations such as JNDIbind, rebind, or unbind, plusCosNamingRead operations. Thespecial-subject, AllAuthenticated, is thedefault policy for this role.242 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!