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

More documents

Recommendations

Info

Table 4-1 Driver Import-Only Parameters Property Name Data Flow Values or Format Bidirectional Application to Identity Vault Identity Vault to Application Enable Entitlements Yes No Use SSL No Data Flow • Bidirectional: Identities are synchronized from both the Identity Vault and the connected system (application). After all pending events are processed, the Identity Vault and connected system mirror each other. • Application to Identity Vault: Identities are synchronized from the connected system (application) to the Identity Vault, but not vice versa. For example, an identity created in the Identity Vault is not created on the connected system unless explicitly migrated. • Identity Vault to Application: Identities are synchronized from the Identity Vault to the connected system (application), but not vice versa. For example, changes made to a connected system’s identity are not synchronized to the Identity Vault. Enable Entitlements Specifies whether the driver uses either Approval Flow or Role-Based Entitlements with the Entitlements Service driver. Enable entitlements for the driver only if you plan to use the User Application or Role-Based Entitlements with the driver. You can use Role-Based Entitlements to integrate the Scripting driver with the Identity Manager User Application. Use SSL Specifies whether the driver uses Secure Sockets Layer (SSL) to encrypt the connection between the Identity Vault and the application. We strongly recommend that you use SSL. If you do not use SSL, identity data (including passwords) is sent across the network in clear text. 26 Identity Manager 4.0.1 Driver for Scripting Implementation Guide
4.1.2 Driver Configuration Page Table 4-2 Driver Configuration Page Property Name Driver Module Driver Object Password Authentication ID Authentication Context Remote Loader Connection Driver Cache Limit Application Password Remote Loader Password Startup Option Values or Format Connect to Remote Loader must be selected. Text Value Not used by the Scripting driver. Not used by the Scripting driver. Parameters Host name or IP address and port number of the driver shim on the connected system, and the RDN of the object with server certificate. The recommended value is 0 (zero). Not used by the Scripting driver. Text Value Auto start Manual Automatic Loopback Detection Yes No Script Command Script Trace File Subscriber Script Polling Script Heartbeat Script Polling Interval Heartbeat Interval Text Value Filename Filename Filename Filename Number of seconds Number of seconds Driver Object Password The Driver object password is used by the driver shim (embedded Remote Loader) to authenticate itself to the Metadirectory engine. This must be the same password that is specified as the Driver object password on the connected system driver shim. Configuring the Scripting Driver 27
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 20 and 21: 8 If you select Perl, you are optio
Page 22 and 23: 3.2.4 Running the Script Service fo
Page 24 and 25: Removing an Instance To remove an i
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?