Why and when to perform this task
You can decide whether to enable IBM WebSphere Application Server security. You must enable global security for all other security settings to function.
WebSphere Application Server uses cryptography to protect sensitive data and to ensure confidentiality and integrity of communications between WebSphere Application Server 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.
WebSphere Application Server uses Java Secure Sockets Extension (JSSE) and Java Cryptography Extension (JCE) libraries in the Software Development Kit (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.
The Unrestricted JCE Policy files for SDK 1.4 Web site is displayed.
Steps for this task
For more information, see Enabling security for all application servers. It is important to click Security > Global security and select the Enable global security option and to save the configuration to the repository. Verify that the validation that occurs after you click OK in 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. Reconfigure the security settings until validation is successful.
START dmgr_proc_name,JOBNAME=server_short_name,ENV=cell_short_name.node_short_name.server_short_nameAfter the deployment manager initialization is complete, go back into the administrative console to complete this task. Remember that security now is enabled in only the deployment manager. If you enabled single signon (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.
./wsadmin.sh -conntype NONEAt the prompt, enter securityoff.
Related concepts
Global security and server security
Java 2 security policy files
Related tasks
Selecting a user registry
Configuring the Lightweight Third Party Authentication mechanism
Enabling security for all application servers
Related reference
Java 2 security