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

More documents

Recommendations

Info

1.2.1 Data Flow Filters and policies control the data flow of identities to and from the connected system and the Identity Vault. The Data Flow option, specified during driver import, determines how these filters and policies behave. • Bidirectional: Sets classes and attributes to be synchronized on both the Subscriber and Publisher channels. • Application to Identity Vault: Sets classes and attributes to be synchronized on the Publisher channel only. • Identity Vault to Application: Sets classes and attributes to be synchronized on the Subscriber channel only. 1.2.2 Policies The Metadirectory engine uses policies to control the flow of information into and out of the Identity Vault. Policies can be customized to support desired operations. The following table describes the policy functions for the Scripting driver in the default configuration: Table 1-1 Default Linux and UNIX Driver Policy Functions Policy Mapping Publisher Event Publisher Matching Publisher Create Publisher Placement Publisher Command Subscriber Matching Subscriber Create Subscriber Command Subscriber Output Subscriber Event Description Maps the Identity Vault objects and selected attributes to connected system objects and attributes. Processes Publisher-side operations. Restricts privileged accounts and defines matching criteria for placement in the Identity Vault. Defines creation rules for provisioning into the Identity Vault. Defines where new objects are placed in the Identity Vault. Defines password publishing policies. Defines rules for matching identities in the connected system. Defines required creation criteria. Transforms attributes and defines password subscribing policies. Sends e-mail notifications for password failures and converts information formats from the Identity Vault to the connected system. Restricts events to a specified container. 14 Identity Manager 4.0.1 Driver for Scripting Implementation Guide
2Planning for the Scripting Driver 2 The planning process for the Novell ® Identity Manager Driver for Scripting begins by determining whether you develop your own scripts and policies for use with your external account management system or you obtain them from a third party. If you are customizing the scripts, the process continues by installing the Scripting driver to a development system. The first decision to make is whether you run the driver shim on Windows or a Linux/UNIX system. (The driver engine component hosted by Novell Identity Manager can run on any operating system that supports Identity Manager.) The driver shim should be installed on a system that hosts, or is remotely connected to, the external account management system. The operating system of this system is the operating system of the driver shim. Your operating system choice determines what scripting language to use. On Linux and UNIX, prewritten libraries are included for Bourne shell, Perl and Python*. On Windows, libraries are included for Microsoft VBScript and PowerShell*. Also, with additional development work, you can port these libraries to another scripting language. Continue the development process by reading Chapter 5, “Customizing the Scripting Driver,” on page 35 and following its instructions. If you have obtained custom scripts from a third party, you should follow their instructions for installing the Scripting driver and their custom components.You should install and test the driver on a test system first and then on production systems. This section reviews some of the issues to consider before you install the Scripting driver. Major topics include • Section 2.1, “Prerequisites for Linux and UNIX Scripting,” on page 15 • Section 2.2, “Prerequisites for Windows Scripting,” on page 16 • Section 2.3, “Establishing a Security-Equivalent User,” on page 17 For general information about planning for identity management, see the Identity Manager 3.6.1 Installation Guide. 2.1 Prerequisites for Linux and UNIX Scripting Topics in this section include • Section 2.1.1, “Identity Vault Server Requirements,” on page 15 • Section 2.1.2, “Supported Operating Systems,” on page 16 • Section 2.1.3, “Other Software,” on page 16 2.1.1 Identity Vault Server Requirements • Novell Identity Manager 3.5.1. Planning for the Scripting Driver 15
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 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 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?