To Configure Security Settings

The Administration Console enables you to set a variety of system-wide security settings.

  1. In the navigation tree, expand the Configuration node.
  2. Under the Configuration node, select the Security node.

    The Security page opens.

  3. Select the Security Manager Enabled checkbox to turn on the security manager.

    If this option is enabled, a JVM option, -Djava.security.manager, will be added to the JVM settings of the Enterprise Server. See To Configure the JVM Options. You must restart the server to enable this change.

    Ensure that you have granted correct permissions for all applications. You can turn off the security manager to enhance performance. This option is disabled by default.

  4. Select the Audit Logging Enabled checkbox to turn on audit logging.

    If this option is enabled, the server will load and run all the audit modules selected in the Audit Modules list. If this option is disabled, the server will not access audit modules. This option is disabled by default.

  5. From the Default Realm drop-down list, select an active realm that the server will use for authentication.

    Applications will use this realm unless they specify a different realm in their deployment descriptor. All configured realms appear in the list. The default value is file.

  6. (Optional) Specify Default Principal information.
    1. In the Default Principal field, type the default user name.

      The server uses this user name when no other principal is provided.

    2. In the Default Principal Password field, type the password of the default principal specified in the Default Principal field.
  7. From the Audit Modules list, select the modules that will be used by the audit subsystem.

    A module listed here must already be configured. If Audit Logging is enabled, this setting must list audit modules. By default, the server uses an audit module named default. For information on creating new audit modules, see To Create an Audit Module.

  8. Select the Default Principal To Role Mapping Enabled checkbox to apply a default principal-to-role mapping to applications that do not have an application-specific mapping.
  9. In the Mapped Principal Class field, type the name of a customized java.security.Principal implementation class to be used in the default principal-to-role mapping.
  10. (Optional) In the Additional Properties section, specify additional properties.

    Valid properties are dependent on the type of realm selected in the Default Realm field.

  11. Click Save.
See Also