User guide

Chapter 7: Developing Applications
7-24
File Encoding for Security Policy File
When a character other than alphanumeric characters and symbols is used in a security policy file, store
the security policy file with the following file encoding format:
• JDK1.3
JavaVM default encoding format
• JDK1.4
UTF-8 encoding format format or the default encoding format used by JavaVM
To use the default encoding format, the system property com.sun.security.policy.utf8 should be
assigned the value false.
Granting Permission for Each Distinguished Name that is Unique Within the User SSO
Repository
• JDK1.3
Insert a space after each comma between the attributeType=attributeValue values making up a
principal name.
Example
grant codeBase "file:isssoaction.jar" ,principal
com.sun.security.auth.X500Principal "CN=user001, OU=User, OU=interstage,
O=fujitsu, DC=com" {
permission java.util.PropertyPermission "java.home","read";
};
• JDK1.4
Do not insert a space after each comma between the attributeType=attributeValue values making
up a principal name.
Example
grant codeBase "file:isssoaction.jar" , principal
javax.security.auth.x500.X500Principal "CN=
user001,OU=User,OU=interstage,O=fujitsu,DC=com" {
permission java.util.PropertyPermission "java.home","read";
};
Note
JDK1.3 cannot be used for JAAS authorization using a distinguished name unique within an SSO
repository where a value other than alphanumeric characters and symbols is used. In this situation, use
JDK1.4.
File Description
Specifying a security policy file used in an application that executes JAAS authorization is explained
below. To use the JAAS authorization function, the codes to be processed for each principal and other
codes must be set in different jar files as described in Table 7-14.