• Print |
• E-mail  |
• Bookmark

A thin client may be allowed access to a remote SAS/Integration
Technologies IOM Server when an expired password is provided.  This
problem can occur regardless of the authentication method used to launch
the Object Spawner.  For example,

  /usr/local/sas8/utilities/bin/objspawn -configfile ./objspawn.cfg

or

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

Regardless of which authentication method is used to start the Object
Spawner, to correct the problem the Object Spawner must be started with
an updated SASAUTH authentication module.


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#007277

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#007277


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: