Console users settings and CORBA naming service user settings
Use the Console users settings page to give users specific authority to administer WAS using 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 users settings page to manage CORBA naming service users settings.
To view the Console users administrative console page, click System Administration > Console Users.
To view the CORBA naming service users administrative console page, click Environment > Naming > CORBA Naming Service users.
- User (Console users)
Specifies users.
The users entered must exist in the configured active user registry.
Data type: String - User (CORBA naming service users)
Specifies CORBA naming service users.
The users entered must exist in the configured active user registry.
Data type: String - Role (Console users)
Specifies user roles.
The following administrative roles provide different degrees of authority needed to perform certain WAS administrative functions:
- Administrator
- The administrator role has operator permissions, configurator permissions, and the permission required to access sensitive data including server password, LTPA password and keys, and so on.
- Configurator
- The configurator role has monitor permissions and can change the WAS configuration.
- Operator
- The operator role has monitor permissions and can change the run-time state. For example, the operator can start or stop services.
- Monitor
- The monitor role has the least permissions. This role primarily confines the user to viewing the WAS configuration and current state.
Data type: String Range: Administrator, Configurator, Operator, and Monitor - Role (CORBA naming service users)
Specifies naming service user roles.
A number of naming roles are defined to provide degrees of authority needed to perform certain WebSphere naming service functions. The authorization policy is only enforced when global security is enabled. The following roles are valid: CosNamingRead, CosNamingWrite, CosNamingCreate, and CosNamingDelete.
The names of the four roles are the same with WebSphere Application Server, Advanced Edition V4.0.2. However, the roles now have authority levels from low to high:
- CosNamingRead
- Users can query the WebSphere name space using, for example, the Java Naming and Directory Interface (JNDI) lookup method. The special-subject EVERYONE is the default policy for this role.
- CosNamingWrite
- Users can perform write operations such as JNDI bind, rebind, or unbind, plus CosNamingRead operations. The special-subject ALL AUTHENTICATED is the default policy for this role.
- CosNamingCreate
- Users can create new objects in the name space through operations such as JNDI createSubcontext and CosNamingWrite operations. The special-subject ALL AUTHENTICATED is the default policy for this role.
- CosNamingDelete
- Users can destroy objects in the name space, for example using the JNDI destroySubcontext method and CosNamingCreate operations. The special-subject ALL AUTHENTICATED is the default policy for this role.
Data type: String Range: CosNamingRead, CosNamingWrite, CosNamingCreate and CosNamingDelete