+

Search Tips   |   Advanced Search

 

Securing specific appservers

 

You can customize security to some extent at the appserver level. You can disable administrative security on an appserver.

You can also modify Java 2 Security and some of the other security attributes that are found on the Secure administration, applications, and infrastructure panel. This panel provides access to the cell-level security settings. You cannot configure a different authentication mechanism or user registry on an individual server basis. This feature is limited to cell-level configuration only.

By default, server security inherits all of the values that are configured for cell-level security. To override the cell-level security configuration at the server level, click Servers > Application Servers > server. Under Security, click Server Security and click any of the following links:

SAS is supported only between V6.0.x and previous version servers federated in a V6.1 cell. After modifying the configuration in any of these panels and clicking OK or Apply, the security configuration for that panel or set of panels now overrides cell-level security. Other panels that are not overridden continue to be inherited at the cell-level. However, you can always revert back to the cell-level configuration at any time. You can revert back to the cell-level security configuration by clearing the check box next to any of the following options on the Server security panel:

For more information, see Server and administrative security.

 

Procedure

  1. Start the console for the deployment manager. To get to the console, go to http://host.domain:port_number/ibm/console. If security is disabled, you can enter any ID. If security is enabled, enter a valid user ID and password, which is either the administrative ID that is configured for the user registry or a user ID that is entered as an administrative user. To add a user ID as an administrative user, click System Administration > Console settings > Console users.

  2. Configure cell-level security if you have not configured it previously. Go to Enabling security for detailed steps. After security is configured, configure server-level security.

  3. To configure server-level security, click Servers > Application Servers > server name. Under Security, click Server security. The status of the security level that is in use for this appserver is displayed.

    [This information applies to V6.0.x and previous servers only that are federated in a V6.1 cell.] By default, you can see that your cell-level security configuration, Common Secure Interoperability (CSI), and SAS have not been overridden at the server level. CSI and SAS are authentication protocols for RMI/IIOP security requests. The server-level security panel lists attributes that are on the Secure administration, applications, and infrastructure panel and can be overridden at the server level. Not all of the attributes on the Secure administration, applications, and infrastructure panel can be overridden at the server level, including the user account repository.

  4. To enable administrative security for this appserver, go to the Server-level security panel, select the Security settings for this server override cell settings and the Enable application security options. By modifying the Server-level security panel, these settings override the settings for cell-level security.

  5. Click Apply and Save.

  6. To enable RMI/IIOP security for the appserver, go to the Server-level security panel, select the RMI/IIOP security for this server overrides cell settings option and click Apply. If you select the RMI/IIOP security for this server overrides cell settings option, any changes that you make to the CSIv2 authentication or transport settings override the same settings on the cell level.

 

What to do next

Typically, server-level security is used to disable user security for a specific appserver. However, this can also be used to disable or enable the Java 2 security manager, and to configure the authentication requirements for RMI/IIOP requests both incoming and outgoing from this appserver.

After you modify the configuration for a particular appserver, restart the appserver for the changes to become effective. To restart the appserver, go to Servers > Application servers and click the server name that you recently modified. Click Stop and then Start.

If you disabled security for the appserver, you can typically test a Web address that is protected when security is enabled.

One URL that usually is installed when the DefaultApplication during installation is the snoop application. If the DefaultApplication is installed on the appserver, test that security is disabled by going to the following URL: http://host.domain:9080/snoop. If security is disabled, a prompt does not display. This URL is just one method of validating the configuration. Validate that the configuration is appropriate for your applications.


Server-level security settings

 

Related tasks


Setting up and enabling security