Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

The Java security "sandbox" for Plugin 1.2 and later has more
restrictions for unsigned applets..  If you are getting an error related
to java.net.SocketPermission then this is the Java security "sandbox"
coming into play.  This occurs when the SAS Server and web server are on
different machines.   We recommend using Middleware server in the
production environment, if your web server and SAS server are not
running on the same machine.

Below is an excerpt from the Middleware Server page from the
AppdevStudio Developer's Site.  Information on setup/installation can be
found from this site.   (http://support.sas.com/rnd/appdev/)

Gateway Access:
    the process by which MWS overcomes Applet security restrictions when
    your Web server and SAS server reside on two separate machines. The
    traditional Java security model, known as the Sandbox model, only
    allows unsigned code (such as applets downloaded from
    a Web server) to access the machine from which the applet was
    downloaded (such as the Web server). Gateway Access alleviates this
    problem by placing MWS on the Web server. Any applet request is
    forwarded to MWS, which, in turn, communicates with the SAS server
    as needed. Because the applet does not directly communicate with
    the SAS server, the applet host security restriction is avoided.


You may receive the same error when testing from within the AppDev
Studio build environment.  If this is the case, you can start middleware
server on the local machine.

Two other options are available.

First, you can sign the applet.  This is a good workaround, however, if
the only sandbox security feature that you need to bypass is the
SocketPermission, it is easier to use Middleware Server.  If the applet
needs full permissions on the client, it must be signed.
For information on signing your applets, refer to http://java.sun.com.
JRE 1.3 supports RSA signing which is much simpler.  For information
regarding RSA signing, refer to
http://java.sun.com/j2se/1.4/docs/guide/plugin/developer_guide/rsa_signing.html


Last, you can modify the java.policy file.  This is discouraged  and
should not be used for production/deployment purposes because it would
require manual editing of the java.policy file on each client machine.

For more information on Java security refer to
http://java.sun.com/j2se/1.3/docs/guide/security/index.html

Operating System and Release Information