Console groups and CORBA naming service groups

Use the Console Groups page to give groups specific authority to administer application servers through tools such as the administrative console or wsadmin scripting. The authority requirements are only effective when global security is enabled. Use the common object request broker architecture (CORBA) naming service groups page to manage CORBA Naming Service groups settings.

To view the Console Groups administrative console page, click System Administration > Console Groups.

To view the CORBA naming service groups administrative console page, click Environment > Naming > CORBA Naming Service Groups.

Group (CORBA naming service groups)

Identifies CORBA naming service groups.

The ALL AUTHENTICATED group has the following role privileges: CosNamingWrite, CosNamingCreate, and CosNamingDelete. The EVERYONE group indicates that the users in this group have CosNamingRead privileges only.

Data type: String
Range: ALL_AUTHENTICATED, EVERYONE

Role (CORBA naming service groups)

Identifies naming service group roles.

A number of naming roles are defined to provide the degrees of authority that are needed to perform certain application server naming service functions. The authorization policy is only enforced when global security is enabled.

Four name space security roles are available: CosNamingRead, CosNamingWrite, CosNamingCreate, and CosNamingDelete. The roles have authority levels from low to high:
Cos Naming Read
You can query the application server name space using, for example, the Java Naming and Directory Interface (JNDI) lookup method. The EVERYONE special-subject is the default policy for this role.
Cos Naming Write
You can perform write operations such as JNDI bind, rebind, or unbind, and CosNamingRead operations. The ALL_AUTHENTICATED special-subject is the default policy for this role.
Cos Naming Create
You can create new objects in the name space through operations such as JNDI createSubcontext and CosNamingWrite operations. The ALL_AUTHENTICATED special-subject is the default policy for this role.
Cos Naming Delete
You can destroy objects in the name space, for example using the JNDI destroySubcontext method and CosNamingCreate operations. The ALL_AUTHENTICATED special-subject is the default policy for this role.
Data type: String
Range: CosNamingRead, CosNamingWrite, CosNamingCreate, and CosNamingDelete

Group (Console groups)

Specifies groups.

The ALL_AUTHENTICATED and the EVERYONE groups can have the following role privileges: Administrator, Configurator, Operator, and Monitor.

Data type: String
Range: ALL_AUTHENTICATED, EVERYONE

Role (Console group)

Specifies user roles.

The following administrative roles provide different degrees of authority needed to perform certain application server administrative functions:
Administrator
The administrator role has operator permissions, configurator permissions, and the permission that is required to access sensitive data, including server password, Lightweight Third Party Authentication (LTPA) password and keys, and so on.
Operator
The operator role has monitor permissions and can change the run-time state. For example, the operator can start or stop services.
Configurator
The configurator role has monitor permissions and can change the application server configuration.
Monitor
The monitor role has the least permissions. This role primarily confines the user to viewing the application server configuration and current state.
Data type: String
Range: Administrator, Configurator, Operator, Deployer and Monitor



Related tasks
Authorizing access to administrative roles
Related reference
Administrative console buttons
Administrative console page features
Administrative console scope settings
Administrative console preference settings
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 7:21:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=useccongroup
File name: usec_congroup.html