Overview |
|
Tasks |
|
Security Configuration Dialog Box Tabs |
|
Included with |
Tivoli Service Desk |
TSD Security |
This help topic is concerned with the security
of your Tivoli Service Desk installation. As the TSD
administrator, you determine who can log on to TSD and what users
can do when they use TSD. For more information, see: |
Rights |
Access to TSD functions is controlled by rights. A user or group of users can perform specific functions in TSD only if they have the appropriate rights. Assign the rights necessary for users to perform their jobs, but limit access to sensitive functions by reserving certain rights to selected users. |
Database Security |
Although TSD rights restrict access to TSD functions, TSD relies on the database server to guarantee data security. The TSD database administrator must be involved in setting up appropriate data security because it is possible to view TSD data from other applications. |
Security Configuration dialog box |
Use the Security Configuration dialog box to configure TSD rights for system functions and certain dialog box buttons. In addition, you use this dialog box to configure an application server key for your TSD application. |
Accessing the Security Configuration dialog box |
To access the Security Configuration dialog box, do one of the following:
|
Rights tab |
You can change the names of TSD system rights to make them more descriptive. Also, you can create custom TSD rights. See Maintaining System Rights. You can also grant a selected right to a list of users and groups or view a list of all the users with a selected right. See Maintaining Rights for Users and Groups. |
Buttons tab |
You can restrict access to TSD functions by making some buttons on dialog boxes available only to users with the appropriate rights. See Maintaining Dialog Box Button Rights. |
Server Auth tab |
You configure a server authorization key to ensure that another application cannot use the TSD application server and that each TSD client workstation processes transactions and requests through the correct application server. See Configuring Server Authorization. |