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

More documents

Recommendations

Info

SAS® Integration Technologies: Administrator's Guide (LDAP Version) Enter or specify the following: Name Access Rights is the name of the rule. specifies whether the rule is to allow permissions or deny permissions. indicates the specific actions that are to be allowed or denied. The rights available are Right Read Write Add Delete Search Compare Description Directory data may be read. Directory data may be changed, created, or deleted. Child objects may be created under the specified object. The selected object may be deleted. Directory data may be searched. For example, denying search rights for a user login object prevents users from searching for a particular user login name. Directory data may be used for comparisons. Unlike searches, the information is not displayed as a result of the comparison; only an indication as to whether the search was successful is returned. Selfwrite Specifies whether users can add or delete themselves from a group. Bind Rule specifies the condition that must be met for the rule to take effect. For example, you could specify that the rule be applied if users log on to their own entry in the LDAP directory. See Specifying Bind Rules for details about what information to enter in this field. Security Select OK to create the rule and close the Specify ACI Rule window. 6. When you finish creating or modifying the access permissions, select OK from the Set Access Permissions window. 7. The Set Access Permissions window disappears and the main Administrator window reappears. NOTE: If any items in the tree view were expanded when you opened the Set Access Permissions window, they are all collapsed when you return to the main Administrator window. Setting Access Permissions for an Object 234
Specifying Bind Rules The bind rule lets you specify a bind condition under which the access control information (ACI) rule is applied. For example, you could specify that the ACI rule is applied only when a user binds to the directory using their distinguished name (DN). Note: ACI rules are supported only for the iPlanet (previously Netscape) LDAP server. Enter the bind rule in the Bind Rule field on the Specify ACI Rule window, using one of the following forms: keyword = expression The keyword and expression must match for the statement to be true. keyword != expression The keyword and expression must not match for the statement to be true. The possible keywords and expressions follow. For detailed information on specifying bind rules, see the iPlanet Directory Server Administrator's Guide. Note: Although bind rules are usually specified as ending with a semicolon, do not put a semicolon on the bind rules in this field. The Administrator application adds the semicolon automatically. userdn The expressions that you can use with this keyword are as follows: userdn = "ldap:///dn" Specify a distinguished name or a distinguished name pattern for dn. You may use an asterisk as a wildcard. The rule is true if the user binds using the specified distinguished name or pattern. For example, if you specified userdn = "ldap:///uid=*, o=Alphalite Airways" the expression is true if the user binds using uid=jrush, o=Alphalite Airways, but not if the user binds using uid=jrush, ou=sales, o=Alphalite Airways. userdn = "ldap:///self" The rule is true if the user is accessing the entry for the distinguished name that is used when binding to the directory. For example, a user that binds as uid=jrush, o=Alphalite Airways could access the uid=jrush object. userdn = "ldap:///all" The rule is true for any valid distinguished name that has successfully bound to the directory. userdn = "ldap:///anyone" The rule is true for anyone. This rule permits anonymous access to the directory. userdn = "ldap:///uid=dn || ldap:///uid=dn2" The rule is valid if the user binds using either of the specified distinguished names. Wildcards are not allowed. userdn = "ldap:///o=Alphalite Airways???(ou=sales)(ou=accounting)" The rule is valid if the user's distinguished name is under either ou=sales o=Alphalite Airways or ou=accounting o=Alphalite Airways. groupdn This keyword uses the following expression: groupdn = "ldap:///dn" Specifying Bind Rules 235
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:
Page 185 and 186:
Page 187 and 188:
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 195 and 196: SAS® Integration Technologies: Adm
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 and 234: Creating a Table Data Source A tabl
Page 235 and 236: Adding Person Entries to the Direct
Page 239 and 240: This example allows access to two g
Page 241: Setting Access Permissions for an O
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?