|
|
Common Problems (and Their Solutions) |
Authenticating using CRAM-MD5
Problem: You get an AppletSecurityException when an applet running inside the Netscape Communicator attempts to authenticate using CRAM-MD5 to the LDAP server.
Cause: The Netscape Communicator disables access to the java.security packages. The LDAP provider uses the message digest functionality provided by java.security.MessageDigest for implementing CRAM-MD5.
Solution: Use the Java Plug-in.
Connecting to Arbitrary Hosts
Problem: You get an AppletSecurityException when your applet attempts to communicate with a directory server running on a machine different from the one from which the applet was loaded.
Cause: If your applet is not signed, it can only connect back to the machine from which the applet was loaded.
Solution: If you want to allow the applet to connect to directory servers running on arbitrary machines, you need to sign both your applet and all the JNDI jars that your applet will be using. For information on signing jars, see http://java.sun.com/products/jdk/1.1/docs/guide/security/index.html.
System Properties
Problem: You get an AppletSecurityException when your applet attempts to set up the environment properties using system properties.
Cause: Web browsers limit access to system properties and will throw a SecurityException if you attempt to read them.
Solution: If you need to obtain input for your applet, try using applet params instead.
|
|
Common Problems (and Their Solutions) |