IBM WebSphere V5.0 Security - CGISecurity

Mapping a group to a CosNaming roleThe process of mapping a group to a CosNaming role is the same as formapping groups to the admin role. The difference is that you have to navigate toEnvironment -> Naming -> CORBA Naming Service Groups from the SecurityCenter. The roles that you can apply to a group are also different.Figure 10-6 CosNaming role to group mapping10.4 Configuring a user registryConfiguring a user registry for the application server is closely related to security,although you should note that global security does not have to be enabled inorder to use a user registry configured for WebSphere. For example, you candeploy your application and assign groups and users from the actual userregistry without security being enabled for the application server.A brief description of user registries is provided in “User registry” on page 224.For information regarding the development of a custom registry, refer to“Developing a custom registry” on page 184.When WebSphere performs authentication, it sends a request to the appropriateregistry. This authentication request may be sent under an identity that differsfrom that under which WebSphere is currently running. This request identity mustbe set in the Administrative Console as part of the configuration process.WebSphere Application Server V5.0 provides three types of user registries:► Local OS User Registry► LDAP User Registry244 IBM WebSphere V5.0 Security Handbook