SPD Server User IDs and Passwords That Are Not In Their Default
Location in the LDAP Database
For this configuration, assume that you want to perform LDAP user authentication, but the
SPD Server user IDs and passwords are not in their default locations in the LDAP database.
Assume that all other LDAP settings use the default configuration.
First, add the LDAP option and the LDAPBINDDN= specification, where the
LDAPBINDDN= property setting is ou=people, dc=domain, dc=company, dc=com.
Adding this option and specification results in LDAP user authentication, where the LDAP
server is running at port LOCAL_HOST on the SPD Server host machine. The LDAP
server looks for SPD Server users at the location that corresponds to ou=people,
dc=domain, dc=company, dc=com in its database.
SPD Server User IDs and Passwords That Are Not In Their Default
Location in the LDAP Database and in the LDAP Server That Is Using
TCPIP_PORT
For this configuration, assume that you want to perform LDAP user authentication, the
SPD Server User IDs and Passwords are located at ou=people, dc=domain, dc=company,
dc=com in the LDAP database, and the LDAP server is using the port TCPIP_PORT.
First, add the LDAP option and set the LDAPPORT= port specification to TCPIP_PORT
in your SPD Server parameter file. Then, add the LDAPBINDDN= specification, where
the LDAPBINDDN= property setting is ou=people, dc=domain, dc=company, dc=com.
User authentication is performed where the LDAP server is running at port TCPIP_PORT
on the SPD Server host machine. The LDAP server looks for SPD Server users at the
location that corresponds to ou=people, dc=domain, dc=company, dc=com in its database.
SPD Server Parameter File Configurations for
Auditing
[NO]WHEREAUDIT
Enables audit logs for WHERE clauses that are submitted to SPD Server. The SPD Server
administrator specifies the WHEREAUDIT option in the spdsserv.parm file. Unless this
option is specified in the
spdsserv.parm
file, WHEREAUDIT is not enabled. The
spdslog
message logger logs messages, and the
spdsaud
audit logger logs audits. If you
use the WHEREAUDIT option, both the
spdslog
log file and the
spdsaud
log file will
contain WHERE statement information.
Usage:
WHEREAUDIT;
NOWHEREAUDIT;
The -WHEREAUDIT option enables audit logging for the server, and automatic audit log
file creation by spdsaud. filespec specifies a partial pathname or filename specification that
is used to generate the complete audit filename. For example, if you specified filespec as
/
audit/spds
, the generated filename would appear as follows:
120
Chapter 11 • Setting Up SPD Server Parameter Files
Summary of Contents for Scalable Performance Data Server 4.5
Page 1: ...SAS Scalable Performance Data Server 4 5 Administrator s Guide...
Page 7: ...Part 1 Product Notes Chapter 1 SPD Server 4 5 Product Notes 3 1...
Page 8: ...2...
Page 12: ...6...
Page 63: ...Part 3 Migration Chapter 5 SPD Server 3 x to SPD Server 4 5 Conversion Utility 59 57...
Page 64: ...58...
Page 70: ...64 Chapter 5 SPD Server 3 x to SPD Server 4 5 Conversion Utility...
Page 72: ...66...
Page 76: ...70 Chapter 6 Using the SPD Server Name Server to Manage Resources...
Page 94: ...88 Chapter 7 Administering and Configuring SPD Server Using the SAS Management Console...
Page 98: ...92 Chapter 8 SPD Server SQL Query Rewrite Facility...
Page 116: ...110 Chapter 10 Configuring Disk Storage for SPD Server...
Page 128: ...122 Chapter 11 Setting Up SPD Server Parameter Files...
Page 154: ...148...
Page 198: ...192 Chapter 14 ACL Security Overview...
Page 212: ...206 Chapter 15 Managing SPD Server Passwords Users and Table ACLs...
Page 214: ...208...
Page 224: ...218 Chapter 16 SPD Server Operator Interface Procedure PROC SPDO...
Page 236: ...230 Chapter 18 SPD Server Table List Utility Spdsls...
Page 256: ...250 Chapter 19 SPD Server Backup and Restore Utilities...
Page 264: ...258 Chapter 20 SPD Server Directory Cleanup Utility...
Page 270: ......