Command line tool security

Security roles provide a fine-grained ability to control who can execute which commands. These roles are supported for wsh (see wsh):

wsh commands are divided into two types, server and system. The server commands consist of:

The following is a partial list of the system commands. However, system commands also include commands that are executed as child processes, which include all of the commands in the bin subdirectory of your EAServer installation, such as deploy.bat (Windows) or deploy.sh (UNIX):

If you have the wsh.run.server role, you can execute any server command. If you have the wsh.run.server.get-statistics role, and no other wsh.run roles, then you can run only the get-statistics command. This also applies to the wsh.run.server roles.

These roles are supported for wfs (see wfs):

where .xxx is the name of the subdirectory relative to the EAServer installation directory.

Keep in mind that:

If a user has the wfs.put.server.html role, he or she can put files into the EAServer html subdirectory. If users have the wfs.put.server role, they can put files into any EAServer subdirectory. If users have the wfs.put.system role, they can put files into any directory outside EAServer. System roles do not support the optional directory because it is unclear as to which file system that directory refers.

By default the admin user has these roles: