IBM WebSphere V5.0 Security - CGISecurity

For example: start with minimal security permissions, then run a test and check
which permissions are failing. Add the necessary permissions to the policy file
then run your test again for re-checking. Repeat these steps until you have all the
necessary permissions set. Note that this will only help you to identify the
persmissions you have to set, it will not help to find the right settings for the
permissions.
Security Tools for Java
The Java 2 SDK provides three tools that assist in the deployment of the new
security features.
For more information refer to the documents under the Java 2 SDK directory in
/docs/tooldocs/.
Key and certificate management tool
keytool is a key and certificate management utility, similar to IBM’s ikeyman
utility. The major difference is that the keytool is only a command line utility
without graphical interface; but keytool allows to create certificates for any
Distinguished Name (dn) that you require; unlike ikeyman which has a
predefined dn schema. For online help, launch the keytool with the -help option:
keytool -help
Policy file editing tool
The policytool with a nice GUI assists the user in specifying, generating, editing,
exporting or importing a security policy. The application can be launched from the
command line with the policytool command.
The policytool utility depends on the keystore that is managed by keytool.
JAR signing and Verification tool
The jarsigner tool can be used to digitally sign Java archives (JAR files) and to
verify such signetures. The jarsigner tool can be used from the command-line by
isuing the jarsigner command.
The jarsigner tool depends on the keystore that is managed by keytool.
8.5.1 Java 2 security in WebSphere
The WebSphere Application Server V5 also supports the Java 2 security in order
to harden the Java Virtual Machine runtime environment.
By default, WebSphere Application Server installs a Java 2 SecurityManager and
Java 2 Security is enforced via a default set of policies. The default policies are
those recommended in the J2EE Platform specification.
Chapter 8. Programmatic security 203