Application Security Features

This section includes:

Secure the Reports Server

See My Oracle Support note Secure the Showjobs Web Command in a Non Secured Reports Server in Oracle Reports 11g, ID 1242614.1.

TMS Security

This section provides information for securing the TMS application, users, and data.

Use Data Access Groups to Restrict Access to the Application

In TMS, database roles dictate which windows in the user interface a user can access. For users assigned to one or more Data Access Groups (DAGs), their assignments dictate the data they see in TMS windows and in the HTML Browser, and whether or not they can operate on TMS data in specific dictionaries and/or domains. You define DAGs in the Maintain DAGs window and then assign users to the group either in the User Assignments tab of the Maintain DAGs window or as you create user accounts. For more information, see the Oracle Thesaurus Management System User's Guide.

Enforce Password Security

Each password should meet or exceed the minimum requirements for the application. For example, a password may need to:

  • Contain a minimum of eight characters.

  • Contain at least one upper case character, and one alphanumeric character.

For more information, see the documentation for the application you are configuring.

Oracle enables a database administrator to enforce various rules about passwords at the database level, including setting a password lifetime, after which users must set a new password; disallowing reuse of previous passwords; locking an account after a user attempts to log on a specified number of times; and creating complexity rules for passwords through a PL/SQL function. For more information, see the Oracle Thesaurus Management System Installation Guide.

Database Roles and Menu-Based Security

TMS includes predefined roles that you can assign to users. A predefined role determines the functions and menu options that are available to a user. You can enforce security by assigning users only the database roles they need to do their work, preventing them from seeing other parts of the system and taking actions they are not authorized to take.

You can also create custom database roles, which may be required if the database roles that are supplied as part of the installation do not fit or cannot be modified to fit your business model.

For more information, see the Oracle Thesaurus Management System User's Guide.