Since the TDM GUI authenticates users via LDAP, all TDM users must be defined in the LDAP application.
There are three main types of TDM users, each with different permissions for different activities.
Note that all TDM windows can be accessed by all users in View mode. However, only authorized users with the relevant permissions can update TDM definitions.
The Admin can execute all activities in the TDM GUI application. Admins are defined as admin in the TDM config.js. Their user and password are authenticated via LDAP.
Admins usually also define the TDM implementation in Fabric. They can execute all activities in the TDM GUI and are responsible for the following activities:
The Environment Owner is the owner of a TDM testing environment. Admins can define one or several Environment Owners for each testing environment. Environment Owners must be defined in LDAP under a dedicated group of users that can be assigned as Environment Owners.
The TDM application identifies users with Environment Owners permissions by their LDAP group.
Environment Owners can execute the following activities in their environment:
Note that Environment Owners cannot add or delete an environment and cannot add or remove Environment Owners from the environment.
Testers can create, extract or load tasks based on their role.
Since the TDM GUI authenticates users via LDAP, all TDM users must be defined in the LDAP application.
There are three main types of TDM users, each with different permissions for different activities.
Note that all TDM windows can be accessed by all users in View mode. However, only authorized users with the relevant permissions can update TDM definitions.
The Admin can execute all activities in the TDM GUI application. Admins are defined as admin in the TDM config.js. Their user and password are authenticated via LDAP.
Admins usually also define the TDM implementation in Fabric. They can execute all activities in the TDM GUI and are responsible for the following activities:
The Environment Owner is the owner of a TDM testing environment. Admins can define one or several Environment Owners for each testing environment. Environment Owners must be defined in LDAP under a dedicated group of users that can be assigned as Environment Owners.
The TDM application identifies users with Environment Owners permissions by their LDAP group.
Environment Owners can execute the following activities in their environment:
Note that Environment Owners cannot add or delete an environment and cannot add or remove Environment Owners from the environment.
Testers can create, extract or load tasks based on their role.