...

Users with administrator privileges can access User Administration (pstsec)Administration, which is an interface for performing the following tasks:

• Adding or removing users from the database
• Defining user groups
• Granting and managing user and user group permissions
• Connecting to your organization's user directories (see Configuring LDAP)

...

Choose User Administration from from the settings drop-down menu to open the User Administration page:

Image Modified

There are two basic steps for managing users in DTP: 

1. Adding users to the database. You can add users manually or sync DTP with your LDAP system, which imports users from your company directory into the database.  
2. Configuring permission and groups. You can specify custom permissions for each user or add them to groups, which enables you to define a set of permissions once and add users accordingly.  

...

Open one of the following addresses in your browser to access the User Administration module:

• http://<host>:8080/pstsec for HTTP
• https://<host>:8843/pstsec for HTTPS

Image Removed

By default, User Administration is configured to run on localhost. The User Administration module will automatically display the Users panel. Log in with user who has administrative access (or is member of EM Administrator group). Only administrators can access the instance of User Administration shipped with License Server. 

See Authentication if you want to configure License Server to authenticate against an instance of User Administration deployed to a different machine.

If you deployed the User Administration module shipped with CTP, you can access User Administration from the Security Configuration page:

1. Choose Security Configuration from the administration menu (gear icon).
2. Click the Browse User Administration on <host> link.
   Image Removed

...

Default Admin User

The user appointed to manage your Parasoft infrastructure should have administrative permissions assigned at the beginning of the security configuration. Those permissions include the following:

...

Permissions refer to the type of access a user has to a specific functionality. The permission format includes the applicable tool, name of the permission type, and permission value (tool:name:value). The following example gives a user provision access in CTP:

em:role:provision  

For example, the Report Center module in DTP is referred to as "grs", so the following permission grants access to Report Center data for a project called "Core":

...

Inherited user permissions are grouped and reflect the permission group hierarchies. Any permission can be disabled/enabled based on specific needs. Permissions inherited by a user from different permission groups are separated but linked with the individual permissions.

Permissions

Administrators can assign the following permissions. 

PST Permissions

PST permissions (Parasoft permissions) provide basic access to the core system.  

basicAccess

Required to login, but additional permissions are necessary to specify which features the user can access.

Values:

• true 
• false 

administration

Grants access to the DTP License so the user can deploy and manage DTP applications.

Values:

• true 
• false 

PSTSEC Permissions

PSTSEC permissions(Parasoft security) provide access to User Administration functionality. 

basicAccess

Required to log into User Administration. Provides ability to modify one's own personal data, but no one else’s.

Values:

• true 
• false 

administration

Grants right to edit and modify user and permission groups data.

Values:

• true 
• false 

GRS Permissions

GRS permissions (group reporting system) provide access to Report Center data, dashboards, source code, etc.  

basicAccess

Required to login to Report Center, but additional permissions are necessary to specify which features the user can access.

Values:

• true 
• false 

administration

Grants access to Report Center administration pages

Values:

• true 
• false 

editGlobalTestConfig

Setting to false prevents users from editing global test configurations. If the permission is not set, project leaders will be able to edit global test configurations, but users with basic permissions will not be able to edit global test configurations.

Values:

• true 
• false 

project

Grants access to the data associated with a specific project. You can use a regular expression to grant access to related projects. For example, if grs:project:Core provides access to a project called Core, you can use the regular expression grs:project:Core \d\.\d to provide access to Core 1.0, Core 1.1, etc. projects.

Values:

• <project name> 
• <regex pattern> 

prioritizeAll

Enables the user to set the priority of violations associated with the project. Team default permission: Leader (leader inherits permissions from member).

Values:

• <project name> 
• <regex pattern> 

prioritizeOwner

Enables the user to set the priority of violations assigned to the user.

Values:

• <project name> 
• <regex pattern> 

viewSourceCode

Enables the ability to view source code associated with the project. Team default permission: Member.

Values:

• <project name> 
• <regex pattern> 

License Server Permissions

License Server permissions provide access to License Server functionality (see License Server). License Server is available as an integrated feature in DTP or as a standalone application.

basicAccess - Deprecated

This permission has been deprecated and will be removed in a future version of DTP.

administration

Grants access to License Server administration pages to perform license management functions, such as adding, removing, and reserving licenses.

Values:

• true 
• false

EM Permissions

EM permissions (Environment Manager) provides access to Continuous Testing Platform and/or Environment Manager (legacy). Permissions for EM are role-based. Choose Role from the Name menu and assign one of the following roles:

administration

Grants access to all CTP activities: testing privileges, provisioning environments, defining systems and environments, controlling access permissions, and test data management. See the CTP User Guide for additional information.

system

Grants the ability to provision environments and to create and execute test jobs in CTP. Appropriate permissions to the resources is required for both actions. This role also grants the ability to execute all repository actions on test data. See the CTP User Guide for additional information.

provision

Grants the ability to provision environments for sources the user has access to in CTP. This role also grants read-only access to test data. See the CTP User Guide for additional information.

Built-in User Groups

...

PST Basic Access

This group defines basic permissions. Each newly created user is automatically assigned as a member of this group. The membership of this group allows users to login to Report Center, but it does not allow access to the administration controls within these modules. Additional permissions are required to perform any actions.

PST Administration

This group defines administration permissions. Members of this group are granted administration permissions for applications within DTP (Report Center, License Server, and User Administration) and can manage data available through administration pages.

GRS Administrators

This group defines administration permission for Report Center. Members of this group can access administration pages for edits, modifications, and management.