Managing users and groups
The Netcool®/Impact configUsersGroups script
is used to manage users and groups within the Liberty Core platform.
About this task
When you run either the
mapRoles script or the configUsersGroups script, Liberty performs
a dynamic update so that a server restart is not required. CPU usage can be affected during the
dynamic update procedures. Dynamic update procedures are typically fine for small environments
without many users and without many required updates. However, when a large environment with an
extensive user base requires changes, it is best to use a central user repository such as LDAP or
ObjectServer. Using LDAP or ObjectServer registry management features, roles can be mapped to
certain user group and do not require any further interaction with the Netcool/Impact
mapRoles or configUsersGroups scripts.
- Add users to Netcool/Impact.
- Add groups to Netcool/Impact.
- Add users to group or groups in Netcool/Impact.
- Update user password in Netcool/Impact.
- Update user group or user groups in Netcool/Impact.
- Delete user from Netcool/Impact.
- Delete group or groups from Netcool/Impact.
- List all users in Netcool/Impact.
- List all groups in Netcool/Impact.
- List all groups that a user is a member of.
- List all users within a group.
If you use an external user repository (LDAP or Object Server) for user authentication, the
configUsersGroups script cannot be used. In this scenario, you create the users and
groups in the external user repository and then map them to roles within Netcool/Impact by using the
mapRoles script.
Procedure
What to do next
If the user is using the same Netcool/Impact directory for their GUI Server and their Impact Server, then they share users and passwords. For login and use of the GUI Server, add the users, groups, and roles to the GUI Server. If you use OSLC, the users, groups, and roles must be added to the Impact Servers.
The registry is stored in the basicRegistry.xml file,
which is in <$IMPACT_HOME>/wlp/usr/shared/config/basicRegistry.xml.
When changes are made to this file, a previous version is backed up
in the <$IMPACT_HOME>/backup directory. The
log file can be in <$IMPACT_HOME>/logs/configUsersGroups.log.
A restart of the server is not needed.