Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Set up, enabling and migrating security > Enable security


Enable security for the realm

WAS uses cryptography to protect sensitive data and to ensure confidentiality and integrity of communications between WAS and other components in the network. Cryptography is also used by Web Services Security when certain security constraints are configured for the web services application.

WAS uses Java Secure Sockets Extension (JSSE) and Java Cryptography Extension (JCE) libraries in the SDK to perform this cryptography. The SDK provides strong but limited jurisdiction policy files. Unrestricted policy files provide the ability to perform full strength cryptography and to improve performance.

Fix packs that include updates to the SDK might overwrite unrestricted policy files. Back up unrestricted policy files before you apply a fix pack and reapply these files after the fix pack is applied.

WAS provides a SDK 6 that contains strong, but limited jurisdiction policy files. We can download the unrestricted policy files from the following website: IBM developer kit: Security information.

Fix packs that include updates to the SDK might overwrite unrestricted policy files. Back up unrestricted policy files before you apply a fix pack and reapply these files after the fix pack is applied.

Your country of origin might have restrictions on the import, possession, use, or re-export to another country, of encryption software. Before downloading or using the unrestricted policy files, check the laws of your country, its regulations, and its policies concerning the import, possession, use, and re-export of encryption software, to determine if it is permitted.

Complete the following steps to download and install the new policy files:

  1. Click Java SE 6

  2. Scroll down the page then click IBM SDK Policy files.

    The Unrestricted JCE Policy files for SDK 6 website displays.

  3. Click Sign in and provide your IBM.com ID and password.

  4. Select Unrestricted JCE Policy files for SDK 6 and click Continue.

  5. View the license and click I Agree to continue.

  6. Click Download Now.

  7. Extract the unlimited jurisdiction policy files that are packaged in the compressed file. The compressed file contains a US_export_policy.jar file and a local_policy.jar file.

  8. In your WAS installation, go to the $JAVA_HOME/jre/lib/security directory and back up your US_export_policy.jar and local_policy.jar files.
  9. Replace your US_export_policy.jar and local_policy.jar files with the two files that you downloaded from the IBM.com website.

Complete the following steps to enable security for the realm:


Procedure

  1. Enable administrative security in WAS.

    For more information, see Enable security. It is important to click Security > Global security. Select an available realm definition from the list, and then click Set as current. Save the configuration to the repository. Verify that the validation that occurs after you click OK on the Security > Global security panel is successful before continuing. If the validation is not successful and you continue with these steps, you risk the server not starting. Re-configure the security settings until validation is successful.

  2. Send a copy of the new configuration to all of the running node agents . If a node agent fails to get the security-enabled configuration, communication with the dmgr fails, due to a lack of access. The node agent is not security-enabled.

    To force synchronize a specific node, complete the following steps from the administrative console:

    1. Click System administration > Nodes and select the option next to all the nodes. You do not need to select the dmgr node.

    2. Click Full resynchronize to verify that the file synchronization has occurred. The message might indicate that the nodes already are synchronized. This message is OK. When synchronization is initiated, verify that the Synchronized status displays for all nodes.

  3. Stop the dmgr. Manually restart the dmgr from the command line or service. To stop the dmgr, click System administration > Deployment manager and click Stop. This action logs you out of the administrative console and stops the dmgr process.

  4. Restart the dmgr process.

    To restart the dmgr process, locate the WAS_HOME/bin directory and type startManager.bat or startManager.shAfter the dmgr initialization is complete, go back into the administrative console to complete this task. Remember that security now is enabled in only the dmgr. If you enabled single sign-on (SSO), specify the fully qualified domain name of your Web address, for example, http://myhost.domain:port_number/ibm/console. When you are prompted for a user ID and password, type the one that you defined as the administrator ID in the configured user registry.

  5. If the dmgr does not start after enabling security, disable security using a script and restart. Disable security from the DeploymentManager/bin directory: 
    ./wsadmin.sh -conntype NONE
    At the prompt, enter securityoff.

  6. Restart all node agents to make them security enabled. We must have restarted the dmgr in a previous step before completing this step. If the node agent is security-enabled before the dmgr is security-enabled, the dmgr cannot query the node agent for status or give the node agent commands.

    To stop all node agents, complete the following steps:

    1. Go to System administration > Node agents and select the option beside all node agents. Click Restart. A message similar to the following example is displayed at the top of the panel: The node agent on node NODE NAME was restarted successfully.
    2. Alternatively, if you previously did not stop the application servers, restart all of the servers within any given node by clicking System administration > Node agents and by clicking the node agents where to restart all the servers. Click Restart all Servers on Node. This action restarts the node agent and any started application servers.

  7. If any node agent fails to restart, perform a manual resynchronization of the configuration. This step consists of going to the physical node and running the client syncNode command. This client logs into the dmgr and copies all of the configuration files to the node agent. This action ensures that the configuration is security-enabled. If the node agent is started, but is not communicating with the dmgr, stop the node agent by issuing the stopServer command.


Related


Global security settings
Specify extent of protection wizard settings
Security custom properties
Security custom property collection
Security custom property settings
Server and administrative security
Java 2 security
Select a registry or repository
Configure the Lightweight Third Party Authentication mechanism
Enable security


Related


Java 2 security policy files

+

Search Tips   |   Advanced Search