SAS® Integration Technologies: Administrator's Guide (LDAP Version)

More documents

Recommendations

Info

Security For the LDAP server and SAS Integration Technologies, you can implement security using authentication and authorization mechanisms. Authentication is the process of verifying that a person is who they say they are. Authorization is the process of evaluating whether a given user has permission to perform a task (such as read or write) on a given resource. SAS Integration Technologies 9.1 supports Sun ONE Directory Server Version 5.1, Netscape Directory Server 4.12 (also owned by Sun Microsystems, and previously sold under the name iPlanet Directory Server), and IBM Secureway Server Version 3.2.2. To implement security for SAS Integration Technologies, follow these steps: Security 1. Define Person Entries for Authentication. To enable authentication against the LDAP server, you must set up your person entries on the LDAP server. For details, see Defining Person Entries 2. Implement Server Security (optional). If you are using an IOM Bridge server, you can use a SAS Login definition to ensure that only authorized users obtain access to SAS data and processes. The login definition specifies which specific users or groups of users can access the server. For more information, see Defining a SAS Login. 3. Define Access Controls for Authorization. You can update access controls on the LDAP server. Authorization in SAS Integration Technologies is accomplished using access control information (ACI) rules (for the Sun ONE Directory Server and Netscape Directory Server) and access control permissions (for the IBM Secureway Directory Server). For general information about access control, see Sun ONE and Netscape Directory Server Access Control Overview and Secureway Directory Server Access Control Overview. You can also refer to the Sun Product Documentation Web site. (The Sun ONE Directory Server is referred to as iPlanet Directory Server on this page.) For information about using the Integration Technologies Administrator to specify ACI rules for the iPlanet Directory Server, see Setting Access Permissions for an Object and Specifying Bind Rules. For information about using the Integration Technologies Administrator to set access control for the Secureway Directory Server, see Setting Access Control for Objects. Security 226
Adding Person Entries to the Directory Before you define person entries, you should have already started the directory server, updated the schema, and set the basic access control. (For details, see Setting up an LDAP Directory Server.) Person entries are needed in order to make the directory useful to SAS applications. For example, when you update access control, access decisions are based on the Distinguished Name (DN) that the person binds to the directory. SAS software also uses person entries to identify users and to obtain information such as user ID and e−mail address. Some of the options for user data are object class, directory structure, and DN. To add person entries to the directory, follow these steps: Security 1. Select an object class to use for the entries. A common choice is the inetOrgPerson class, which accepts many useful attributes. If you need to add attributes to your person entries and the attributes are not allowed by inetOrgPerson, you can create your own object class using inetOrgPerson as a parent class. 2. Enter the person entries in the directory. Follow these guidelines to help your person data work better with SAS software: ♦ Keep common names unique. Some SAS applications use the common name when associating a person entry with other entries in the SAS application entries. ♦ Include the user ID and e−mail address in the person entry. Applications need to look up the user ID. ♦ When you load the directory with person entries for the first time, add a default userpassword attribute. This attribute allows users to bind to this DN when they use the directory. 3. Decide how the person data is laid out in the directory. The two most popular options are as follows: Flat structure puts all of the data in one place in the directory. The benefit is that you do not have to move the entries if users change organizations within the company. Organizational unit structure places the entries in a subtree according to the organizational unit within the company. This structure can resemble the company's organization, which allows you to visualize the relationships between entries. 4. Decide on the structure of the distinguished names for your person entries. Although your selection of the attribute for the relative distinguished name is not critical, you must be consistent. Two acceptable choices are common name and user ID. If you use a flat structure for the person data, then use user ID for the DN, because common names are duplicated more often than user IDs. Adding Person Entries to the Directory 227
Page 1 and 2:
SAS® 9.1.3 Integration Technologie
Page 3 and 4:
SAS® Integration Technologies: Adm
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Setting up an LDAP Directory Server
Page 13 and 14:
10. You are asked whether you want
Page 15 and 16:
Page 17 and 18:
sasDomainName eq, pres sasLogicalNa
Page 19 and 20:
Adding Person Entries to the Direct
Page 21 and 22:
Using the Integration Technologies
Page 23 and 24:
saschannels sassubscribers Hardware
Page 25 and 26:
If the value is set to none, the LD
Page 27 and 28:
Page 29 and 30:
The command to start the SAS sessio
Page 31 and 32:
Logical names All logical names ass
Page 33 and 34:
Delete Help Server Wizard Set Acces
Page 35 and 36:
Verifying IT Administrator Connecti
Page 37 and 38:
Modifying Objects with IT Administr
Page 39 and 40:
Searching for Objects Using IT Admi
Page 41 and 42:
Reloading (Refreshing) IT Administr
Page 43 and 44:
Choosing a Server Configuration Int
Page 45 and 46:
Page 47 and 48:
Overview of Pooling A workspace poo
Page 49 and 50:
Setting up Workspace Pooling You ca
Page 51 and 52:
Server and Client Requirements SAS
Page 53 and 54:
server and need metadata definition
Page 55 and 56:
Creating the Metadata for a COM/DCO
Page 57 and 58:
When you complete all of the steps
Page 59 and 60:
♦ Enter a unique name (sasServerc
Page 61 and 62:
Configuration File Example: Minimal
Page 63 and 64:
Enabling DCOM on the Server and the
Page 65 and 66:
Configuring SAS for DCOM The COM Se
Page 67 and 68:
Setting Default COM Security on Win
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Setting Default COM Security on Win
Page 77 and 78:
Page 79 and 80:
Setting Permissions per Application
Page 81 and 82:
♦ SAS® Integration Technologies:
Page 83 and 84:
left the Authentication Level on th
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
where is the name of your machine
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Using the SAS Integration Technolog
Page 97 and 98:
Page 99 and 100:
configuration file for a connection
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
3. Select the type of server to tes
Page 109 and 110:
• Make sure the permissions are c
Page 111 and 112:
Object Server Parameters The follow
Page 113 and 114:
Attributes for sasServer The sasSer
Page 115 and 116:
Page 117 and 118:
Attributes for sasLogicalNameInfo T
Page 119 and 120:
How an IOM Bridge Server Works In o
Page 121 and 122:
UNIX Note: When you install the spa
Page 123 and 124:
This completes the basic configurat
Page 125 and 126:
Spawner Requirements Hardware Requi
Page 127 and 128:
• Example UUID Generator IOM Brid
Page 129 and 130:
Using the IT Administrator Wizard t
Page 131 and 132:
◊ If you would like to add anothe
Page 133 and 134:
Using IT Administrator to Define a
Page 135 and 136:
Using IT Administrator to Define a
Page 137 and 138:
IOM Bridge Servers SAS® Integratio
Page 139 and 140:
the sasSpawner Attributes List will
Page 141 and 142:
Configuring a UUID Generator Curren
Page 143 and 144:
The following procedure explicitly
Page 145 and 146:
foundDashDash=1; fi args="$args$tmp
Page 147 and 148:
Invoking (Starting) the Spawner Aft
Page 149 and 150:
Starting the Spawner on Windows To
Page 151 and 152:
♦ ♦ −ldap_binddn "CN=John Doe
Page 153 and 154:
Method 1: Using SAS Setup 1. Log in
Page 155 and 156:
Spawner Invocation Options The foll
Page 157 and 158:
Note: If none of the spawner defini
Page 159 and 160:
Using the SAS Integration Technolog
Page 161 and 162:
Page 163 and 164:
configuration file for a connection
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184: SAS® Integration Technologies: Adm
Page 189 and 190: Configuration File Examples: Server
Page 191 and 192: Configuration File Example: Using L
Page 193 and 194: Configuration File Examples: UUID G
Page 197 and 198: Attributes for sasLogin A SAS login
Page 199 and 200: Attributes for sasServer The sasSer
Page 203 and 204: Object Server Parameters The follow
Page 205 and 206: Server Startup Command You can spec
Page 207 and 208: Attributes for sasSpawner The sasSp
Page 213 and 214: Creating a Stored Process Path A st
Page 215 and 216: 7. List the possible values for the
Page 217 and 218: 2. are discussed separately and in
Page 219 and 220: 6. After you define the subscribers
Page 221 and 222: 7. You cannot deliver information o
Page 223 and 224: Creating Subscribers The publicatio
Page 225 and 226: Creating Subscriptions When you ass
Page 227 and 228: Entry Filters Publishers send infor
Page 229 and 230: Creating Overrides An override is c
Page 231 and 232: Creating a Library Data Source A li
Page 233: Creating a Table Data Source A tabl
Page 239 and 240: This example allows access to two g
Page 241 and 242: Setting Access Permissions for an O
Page 243 and 244: Specifying Bind Rules The bind rule
Page 245 and 246: e before, after, or equal to the ti
Page 249 and 250: Cn=sasArchivePaths,sascomponent=Arc
Page 255: Your Turn If you have comments or s
show all

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

Create successful ePaper yourself

Delete template?

Save as template?