14.01.2013 Views

SAS 9.3 Guide to Software Updates

SAS 9.3 Guide to Software Updates

SAS 9.3 Guide to Software Updates

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Set File Security in UNIX Environments<br />

The login.config file contains login module definitions for connecting <strong>to</strong> <strong>SAS</strong> Remote<br />

Services by using the <strong>SAS</strong> Metadata Server. Because this file contains connection<br />

information, you want <strong>to</strong> restrict access <strong>to</strong> this file. To restrict access <strong>to</strong> the owner of this<br />

file, type the following commands at the UNX prompt:<br />

cd <strong>SAS</strong>-configuration-direc<strong>to</strong>ry/Lev1/Web<br />

chmod go=Common/login.config<br />

Res<strong>to</strong>re Restrictive Policy Settings<br />

If you configured your environment <strong>to</strong> use restrictive policy settings, then you had <strong>to</strong><br />

disable these policy settings before installing your <strong>SAS</strong> software. How you res<strong>to</strong>re these<br />

settings depends on whether <strong>SAS</strong> au<strong>to</strong>matically reconfigured JBoss and whether you<br />

specified <strong>to</strong> use restricted permissions in your initial deployment. Use the following table<br />

<strong>to</strong> determine the post-configuration steps for your site.<br />

Table 13.1 When Post-Configuration Steps Are Required<br />

Type of Configuration Post-Configuration Steps<br />

<strong>SAS</strong> au<strong>to</strong>matically<br />

reconfigures the JBoss<br />

server and re-creates the<br />

restrictive policy file.<br />

If you selected <strong>to</strong> use restrictive permissions the first time you<br />

configured your <strong>SAS</strong> <strong>9.3</strong> deployment, then <strong>SAS</strong> specified the<br />

following options in the start-up script:<br />

n -Djava.security.manager<br />

JBoss Application Server 83<br />

n -Djava.security.policy=full-path-<strong>to</strong>-restrictivepolicy-file<br />

Therefore, you do not need <strong>to</strong> specify these options again.<br />

When <strong>SAS</strong> au<strong>to</strong>matically restarts the JBoss server, the<br />

restricted permissions file should be created and copied <strong>to</strong> the<br />

server.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!