In its default state, an MTS package is not very secure, and therefore its
member components are not secure. Any client on the network can use components
in a package after it is first created. This could potentially be dangerous if
the components expose business-critical functionality, such as performing financial
transactions or providing access to proprietary data. Also, components might be
built to perform administrative actions for an enterprise system. It is easy to
see the need for securing MTS objects.
Adding security is a painless process. For components to be secured, the following
three things must happen:
-
Roles must be created for the package that contains components that require
security.
-
Roles must be assigned to the components that need to be secured.
-
Authorization checking must be enabled for the package
