Identity Manager 4.0.1 Driver for Scripting Implementation ... - NetIQ

More documents

Recommendations

Info

8 If you select Perl, you are optionally asked to install the Perl IDMLib perl module into the Perl system path to be accessible by the sample Perl scripts. Enter Yes or No to install this library. 9 The installation of the driver shim is finished, with the option of starting the Driver Shim Service. Proceed to the next section to complete the installation of the driver. 3.1.2 Creating the Driver in Novell eDirectory using iManager 1 In iManager, click the Import Drivers task under Identity Manager Utilities. 2 All drivers are contained in a Driver Set. You can create a new Driver Set or install the driver into an existing one. See “Creating and Configuring a Driver” in the Identity Manager Administration Guide for more details. Click Next to proceed. 3 Select the Scripting driver from the list of drivers and click Next to proceed. 4 Enter information in the requested configuration fields, then click Next to continue. When entering the Remote Loader and Driver object passwords, be sure to enter the same values that you entered when installing the Drivershim. For more information on these fields, see Section 4.1, “Driver Parameters and Global Configuration Values,” on page 25. 5 Click Define Security Equivalences, and select your administrative user to make the driver security-equivalent to that user (see also Section 2.3, “Establishing a Security-Equivalent User,” on page 17). 6 Click Exclude Administrative Roles, and select your administrative user and other highprivilege users that should not be monitored for events. 7 Click Next to proceed, then click Finish to complete the installation. 3.1.3 Running the Driver Start the driver engine component in Novell iManager. The driver shim is a UNIX daemon process. Use the UNIX startup script usdrvd to start and stop the Novell Identity Manager Linux and UNIX Script Driver (see Chapter 6, “Using the Scripting Driver,” on page 117.) 3.2 Installing the Windows Scripting Driver Topics in this section include • Section 3.2.1, “Installing the Driver Shim,” on page 20 • Section 3.2.2, “Creating the Driver in Novell eDirectory,” on page 21 • Section 3.2.3, “Running the Driver,” on page 21 • Section 3.2.4, “Running the Script Service for PowerShell (optional),” on page 22 • Section 3.2.5, “Running Multiple Instances of the Driver (optional),” on page 23 3.2.1 Installing the Driver Shim 1 Obtain the windows_scriptdriver_install.exe file from your installation media. Run this file on your Windows system. 2 Click Next to continue the installation. 20 Identity Manager 4.0.1 Driver for Scripting Implementation Guide
3 Accept the default installation folder or specify your own. Click Next to continue. 4 Review your settings and click Next to continue. 5 After the driver files are copied, you are prompted to retrieve an SSL certificate. Novell eDirectory must be running to retrieve the certificate. The certificate allows SSL encryption between the Identity Manager engine and the driver shim. Enabling SSL is optional but is recommended for better security. To retrieve the certificate, click Yes and follow the prompts in the console window: 5a Specify the DNS name or IP address of your eDirectory server. 5b Specify the LDAP secure port, default 636. 5c Enter Y to accept the certificate. 6 You are prompted to enter Driver and Remote Loader passwords. These passwords are used to verify that an authorized driver shim is communicating with the Identity Manager engine. Although you don’t need to enter the passwords immediately, they must be set at some point before running the driver. Click Yes to the prompt and follow the prompts in the console window: 6a Enter and confirm the Remote Loader password. 6b Enter and confirm the Driver password. 7 The installation of the driver shim is finished, with the option of starting the Driver Shim Service. Proceed to the next section to complete the installation of the driver. 3.2.2 Creating the Driver in Novell eDirectory 1 In iManager, click the Import Drivers task under Identity Manager Utilities. 2 All drivers are contained in a driver set. You can create a new driver set or install the driver into an existing one. See “Creating and Configuring a Driver” in the Identity Manager 3.6.1 Administration Guide for more details. Click Next to proceed. 3 Select the Scripting driver from the list of drivers, then click Next to proceed. 4 Fill in the requested configuration fields, then click Next to continue. When entering the Remote Loader and Driver Object passwords, be sure to enter the same values that you entered when installing the driver shim. For more information on these fields, see Section 4.1, “Driver Parameters and Global Configuration Values,” on page 25. 5 Click Define Security Equivalences, and select your administrative user to make the driver security-equivalent to that user (see also Section 2.3, “Establishing a Security-Equivalent User,” on page 17). 6 Click Exclude Administrative Roles, and select your administrative user and other highprivilege users that should not be included monitored for events. 7 Click Next to proceed, then click Finish to complete the installation. 3.2.3 Running the Driver Start the driver engine component in Novell iManager. The driver shim is a Windows service. Use the Windows Services application to start and stop the Novell Identity Manager Windows Script Driver service (see Chapter 6, “Using the Scripting Driver,” on page 117). Installing the Scripting Driver 21
Page 1 and 2: AUTHORIZED DOCUMENTATION Implementa
Page 4 and 5: 4 Identity Manager 4.0.1 Driver for
Page 6 and 7: 5 Customizing the Scripting Driver
Page 8 and 9: C.3.3 Publisher Functions . . . . .
Page 10 and 11: For additional documentation about
Page 12 and 13: The Publisher shim of the embedded
Page 14 and 15: 1.2.1 Data Flow Filters and policie
Page 16 and 17: 2.1.2 Supported Operating Systems
Page 18 and 19: Operation [Entry Rights] [All Attri
Page 22 and 23: 3.2.4 Running the Script Service fo
Page 24 and 25: Removing an Instance To remove an i
Page 26 and 27: Table 4-1 Driver Import-Only Parame
Page 28 and 29: Remote Loader Connection Parameters
Page 30 and 31: Property Name Publish Passwords to
Page 32 and 33: Notify the User of Password Synchro
Page 34 and 35: 34 Identity Manager 4.0.1 Driver fo
Page 36 and 37: • What types of identities exist
Page 38 and 39: • Modify-password: An identity’
Page 40 and 41: 5.3 The Connected System Include/Ex
Page 42 and 43: EXCLUDE . . . ENDEXCLUDE You can us
Page 44 and 45: A plus sign (+) indicates that the
Page 46 and 47: Developing a custom driver with She
Page 48 and 49: Table 5-1 Items Name COMMAND ASSOCI
Page 50 and 51: # Removing an association IDMSETVAR
Page 52 and 53: Value Name SEARCH_CLASSES SEARCH_AT
Page 54 and 55: Publisher Script Development Events
Page 56 and 57: Table 5-5 Scripting Driver Paramete
Page 58 and 59: 2. Authenticate by using any userna
Page 60 and 61: For command line tools, you can con
Page 62 and 63: Name DEST_ENTRY_ID ADD_{attr_name}
Page 64 and 65: Returning an Event Status On the Su
Page 66 and 67: Execute the query against the exter
Page 68 and 69: Polling for Application Events The
Page 70 and 71:
Parameter Name Driver/Channel Descr
Page 72 and 73:
5.6.3 Deployment The Scripting driv
Page 74 and 75:
Application Event Monitoring You al
Page 76 and 77:
Name REMOVE_REF_attr_name OLD_PASSW
Page 78 and 79:
Table 5-14 STATUS Subroutines Subro
Page 80 and 81:
Table 5-16 Query Values Value Name
Page 82 and 83:
#!/usr/bin/python import os from id
Page 84 and 85:
Parameter Name Driver/Channel Descr
Page 86 and 87:
Deploying a Custom Driver To deploy
Page 88 and 89:
IDMExecuteIO’s first parameter is
Page 90 and 91:
Value SRC_DN EVENT_ID SRC_ENTRY_ID
Page 92 and 93:
Table 5-21 Query Values Value Name
Page 94 and 95:
If Results(0) = 0 Then Phone = Resu
Page 96 and 97:
functions can be used to retrieve t
Page 98 and 99:
IDMQueryInit IDMQuerySetAssociation
Page 100 and 101:
Directory Description Required File
Page 102 and 103:
# Create an array with two lines $i
Page 104 and 105:
Value SRC_DN EVENT_ID SRC_ENTRY_ID
Page 106 and 107:
Handling Query Events For Query eve
Page 108 and 109:
Handling a query is similar, except
Page 110 and 111:
The response to the heartbeat is im
Page 112 and 113:
Function idm_getqueryinstanceparent
Page 114 and 115:
Deploying a Custom Driver To deploy
Page 116 and 117:
116 Identity Manager 4.0.1 Driver f
Page 118 and 119:
Operating System Windows Command/Ta
Page 120 and 121:
Page 122 and 123:
Ensure that the security certificat
Page 124 and 125:
Page 126 and 127:
Table A-1 Message Priorities Messag
Page 128 and 129:
A.2.1 Driver Shim Installation Fail
Page 130 and 131:
• To provision identities from th
Page 132 and 133:
Page 134 and 135:
Possible Cause: Action: The stateme
Page 136 and 137:
LWS0002I All services are now activ
Page 138 and 139:
Action: Action: Action: Action: Ver
Page 140 and 141:
OAP004E HTTP Error: cause. Explanat
Page 142 and 143:
Possible Cause: Possible Cause: Pos
Page 144 and 145:
IDMTRACE Message Appends the specif
Page 146 and 147:
This is a heartbeat message HEARTBE
Page 148 and 149:
idmsetvar($Name, $Value) Sets a sin
Page 150 and 151:
status(Level, Message) Sends a stat
Page 152 and 153:
C.4 Microsoft VBScript (IDMLib.vbs)
Page 154 and 155:
Function IDMGetSubscriberParam(Para
Page 156 and 157:
Sub IDMQueryInit Initializes a quer
Page 158 and 159:
The Publisher calls Heartbeat.ps1 p
Page 160 and 161:
function idm_writevalue($name, $val
Page 162 and 163:
function idm_querysetreadparent($re
Page 164 and 165:
Page 166 and 167:
5 Click Apply. 6 Restart the driver
Page 168 and 169:
[-r] [-y old-association] [-z new-a
Page 170 and 171:
some new value ^d D.4 Files an
Page 172 and 173:
Page 174:
show all

Identity Manager 4.0.1 Driver for Scripting Implementation ... - NetIQ

Create successful ePaper yourself

Delete template?

Save as template?