Legacy Security Options

In previous releases, Directory Server and Enterprise Server each had independent security schemes. These are still available and can be used in conjunction with the new features or separately.

Legacy Directory Server security

Legacy Directory Server security controls access to the administration screens through the use of user, group and permission definitions stored within the Directory Server repository. It also controls application access to configuration information. For example, an enterprise server reads its configuration information from Directory Server. To do this, it requires suitable user credentials to access Directory Server.

This security model is supported with the Enterprise Server External Security Facility through a special ESM. The ESM uses the same user and group definitions and the same permissions.

Legacy MTO Security

Legacy Enterprise Server security controls access to MTO transactions and resources. It uses details stored in Sign-on table (SNT), transation and resource definitions.

If there are no security managers on the security manager list that it uses, an enterprise server will use this legacy MTO security model. (Note that this legacy model is only active if you have defined within ESMAC a user called mfuser checked the Local ES Security enabled option for that user.) Alternatively, you can obtain the legacy security behaviour by using the special casesm ESM module. This module acts as a security manager, providing all of the legacy Enterprise Server security features.