WAS v8.5 > Secure applications > Secure Client applicationsConfigure secure access to resources for applet clients
By default, the applet client is configured to have security enabled. If we have administrative security turned on at the server from which we are accessing resources, then we can use secure sockets layer (SSL) when needed.
If you decide the security requirements for applet client applications differ from other types of client applications, then create a new version of the sas.client.props and ssl.client.props files.
- Make a copy of the following files so that we can use them for an applet:
<app_client_root>\properties\sas.client.props
<app_client_root>\properties\ssl.client.props
- Edit the copies of the sas.client.props and ssl.client.props files made with your changes.
- Display the IBM Control Panel for Java. Click Start > Control panel, then select the product Java Plug-In.
- To use the files you created in step 1, modify the following Java Run-Time parameter values. Click the Advanced tab, then edit the parameters in the Java Runtime Parameters field:
-Dcom.ibm.CORBA.ConfigURL=file:<app_client_root>\properties\sas.client.props
-Dcom.ibm.SSL.ConfigURL=file:<app_client_root>\properties\ssl.client.props
- To save your changes, click Apply
Subtopics
- Applet client security requirements
When code is loaded, it is assigned permissions based on the security policy in effect. This policy specifies the permissions available for code from various locations. We can initialize this policy from an external policy file.