• Print |
• E-mail  |
• Bookmark

If a SAS client supplies a blank or empty password to connect to a
remote SAS server, the client may fail to authenticate.  On some
systems, it is valid for a user to enter a blank or empty password to
access the remote server.

This problem is likely to occur if the SAS server was started with
SASAUTH authentication.  For example, starting the SAS/Integration
Technologies Object Spawner with SASAUTH authentication:

   /usr/local/sas8/utilities/bin/objspawn -authprog ./sasauth

Known SAS clients that may encounter this problem include:

  Enterprise Guide
  SAS/CONNECT
  SAS Integration Technologies (VB, Java, etc.)
  SAS Information Delivery Portal
  SAS/SHARE

To correct the problem, the SAS server must be started with an updated
SASAUTH authentication module (available in an upcoming hotfix).

A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#010238

For customers running SAS with Asian Language Support (DBCS), this
hot fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#010238


ATTENTION (1):  If you are using the sasauth authentication module with
the Integration Technologies object spawner, then you must also install
hotfix

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#82IH15


Customers running in a DBCS environment should download

http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#82IH15



ATTENTION (2):  If you are using the sasauth authentication module with
the SAS/CONNECT job spawner, then you must also install hotfix

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#82BB95


Customers running in a DBCS environment should download

http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#82BB95

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for Release 8.2 (TS2M0) with Asian Language Support (DBCS) for this issue is available at:

A fix for Release 8.2 (TS2M0) with Asian Language Support (DBCS) for this issue is available at:

A fix for Release 8.2 (TS2M0) with Asian Language Support (DBCS) for this issue is available at: