Sun Microsystems 819468310 用户手册
5. If you are using a JDK version earlier than JDK 1.5, edit the
jdk_root/jre/lib/security/java.security file and add Bouncy Castle as one of the
providers. For example:
providers. For example:
security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider
6. Set the following property in the AMConfig.properties file to true:
com.sun.identity.jss.donotInstallAtHighestPriority=true
7. Restart the Access Manager web container.
For more information, refer to problem ID 5110285 (XML encryption requires Bouncy Castle
JAR file).
JAR file).
Documentation Updates
To access these documents, see the Access Manager 7.1 collection:
A new document entitled Chapter 1, “Technical Note: Deploying Access Manager Instances to
an Application Server Cluster,” in Technical Note: Deploying Access Manager to an Application
Server Cluster has been added to the Access Manager 7 2005Q4 collection.
an Application Server Cluster,” in Technical Note: Deploying Access Manager to an Application
Server Cluster has been added to the Access Manager 7 2005Q4 collection.
The Sun Java System Access Manager Policy Agent 2.2 collection has also been revised to
document new agents:
document new agents:
Redistributable Files
Sun Java System Access Manager 7.1 does not contain any files that you can redistribute to
non-licensed users of the product.
non-licensed users of the product.
Documentation Updates
Sun Java System Access Manager 7.1 Release Notes • March 2007
34