moduser (mu)
Description
Modify user information such as permissions, user ID, and name for an AppScan® Source user.
Syntax
moduser --userid|-u <user id>
[--fullname|-f <user first and last name>]
[--group [group[:permission[;permission...]
[--group...]]
[--removegroup [group[:permission
[;permission...] [--removegroup...]]
User name and name
--username|-u
: Required. A valid AppScan Source user name.--fullname|-f
: Optional. Full name of the user. If the entry includes spaces, enclose it with"
symbols (for example,-f "Joe Smith"
).
Groups and Permissions
Optional.
Groups and permissions identify the allowable AppScan Source tasks for that user. Tasks not specifically identified as part of a permission are available to all users:
--group
: The groups
and group permissions to add for this user. Specifying a group without
any permissions grants the user all permissions in that group.
or
--removegroup
:
The groups and group permissions to remove from this user. Specifying
a group without any permissions removes all permissions in that group.
The groups and permissions are:
ASSESSMENTS
: Assessment level permissions.ASMNTDELETE
: Delete published assessments.ASMNTPUBLISH
: Publish assessments.ASMNTSAVE
: Save assessments.ASMNTVIEWPUBLISH
: View published assessments.
ADMIN
: Administrative permissions.ASE
: Manage AppScan Enterprise settingsUSER
: Manage user settings including adding and deleting users and changing user permissions.
APPS
: Application and Project level permissionsATTRAPPLY
: Apply attributes to applications.ATTRMODIFY
: Create, delete, and modify attributes.VIEWREGISTER
: View registered applications and projects.REGISTER
: Register/unregister applications and projects. ImpliesVIEWREGISTER
permission.SCAN
: Scan applications and projects.
KB
: Knowledgebase management permissions.CUSTOM
: Manage custom rules.PATTERN
: Create, edit, or delete patterns.
FILTER
: Filter managementSHAREDFILTERS
: Manage shared filters.
SCANCONFIG
: Scan configuration managementSHAREDCONFIGS
: Manage shared scan configurations.
Example
After Joan Darcy's user credentials
were created (with the newuser (nu)
command),
the System Administrator determined that she only needs save, publish,
and view permissions; but not delete permission. Additionally, Joan
needs Knowledgebase Patterns
permissions:
moduser --userid joandarcy --removegroup
ASSESSMENTS:ASMNTDELETE --group KB:PATTERN