Console users settings and CORBA naming service user settings
Use the Console users settings page to give users specific authority
to administer WebSphere Application Server 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.
- User (CORBA naming service users)
- Specifies CORBA naming service users.
The users entered must exist in the configured active user registry.
- Role (Console users)
- Specifies user roles.
The following administrative roles provide different degrees of authority
needed to perform certain WebSphere Application Server administrative functions:
- Administrator
- The administrator role has operator permissions, configurator permissions,
and the permission required to access sensitive data including server password,
Lightweight Third Party Authentication (LTPA) password and keys, and so on.
- Configurator
- The configurator role has monitor permissions and can change the WebSphere
Application Server 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 WebSphere Application Server 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 Version 4.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 |

Administrative console buttons
Administrative console page features
Administrative console scope settings
Administrative console filter settings
Administrative console preference settings
Searchable topic ID:
usecconuser
Last updated: Jun 21, 2007 8:07:48 PM CDT
WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/usec_conuser.html