Usage Note 36979: SAS® 9.2 Stored Processes use client accounts for database access
When running a SAS® Stored Process in SAS 9.2, a client user account is used to connect to a database library that is defined in a SAS® Metadata Repository if the library is assigned with a LIBNAME statement in the SAS Stored Process source code. However, if the library is preassigned or defined in an autoexec file, the SAS General Server login account sassrv is used.
In SAS® Management Console, the client user must have a login account that is a valid account for database access (or be a member of a metadata group that has such an account) unless another user identity is specified when accessing the library. The Authentication Domain of this account must match the Authentication Domain of the database.
As an example, if a SAS Stored Process contains the following statement:
libname oralib meta library="my ora library";
Then, the following conditions must be true:
- The client user must have metadata permission to access the ORALIB library.
- In SAS Management Console under User Manager the client user must have a login user account that has database permission (granted by the database administrator) to connect to the database (or be a member of a metadata group that has such an account). The password for this account must be specified.
The Authentication Domain of this account must match the Authentication Domain of the database. As an example, if the ORALIB library has an Authentication Domain called OraAuth, then the client user account must also have an Authentication Domain called OraAuth.
If you want to access a database library using a different user identity, you can specify the USER= and PASSWORD= options in the LIBNAME statement. The specified user must have a valid account for database access.
If you are using Integrated Windows Authentication (IWA) when connecting to a Microsoft SQL Server database, the client user account is not used. Instead, the sassrv account (SAS General Servers login account) is used. This is an exception to the information provided above.
If you are using Kerberos when connecting to a database, the client user account is not used. Instead, the sassrv account (SAS General Servers login account) is used. This is an exception to the information provided above
For more information about client access to metadata resources, see SAS Note 36919, "SAS® 9.2 SAS® Stored Processes use client credentials for SAS® Metadata Server access."
Operating System and Release Information
SAS System | SAS Integration Technologies | z/OS | 9.2 TS2M0 | |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M0 | |
Microsoft Windows XP 64-bit Edition | 9.2 TS2M0 | |
Microsoft® Windows® for x64 | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M0 | |
Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M0 | |
Microsoft Windows Server 2008 | 9.2 TS2M0 | |
Microsoft Windows XP Professional | 9.2 TS2M0 | |
Windows Vista | 9.2 TS2M0 | |
64-bit Enabled AIX | 9.2 TS2M0 | |
64-bit Enabled HP-UX | 9.2 TS2M0 | |
64-bit Enabled Solaris | 9.2 TS2M0 | |
HP-UX IPF | 9.2 TS2M0 | |
Linux | 9.2 TS2M0 | |
Linux for x64 | 9.2 TS2M0 | |
OpenVMS on HP Integrity | 9.2 TS2M0 | |
Solaris for x64 | 9.2 TS2M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When running a SAS® Stored Process in SAS® 9.2, the client user account is used to connect to a database library that is defined in the SAS® Metadata Repository.
Date Modified: | 2019-08-02 16:41:50 |
Date Created: | 2009-08-25 15:35:04 |