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

More documents

Recommendations

Info

• Modify-password: An identity’s password has changed. This event type can be considered a subtype of Modify, but because it often requires special handling, it is treated as a separate event type. • Delete: An identity is destroyed. This might mean permanent deletion, or a change of status of the identity so that it can be undeleted if necessary. This might affect other identities. For example, deleting a User that is a member of a Group might cause a Modify event for that Group. • Rename: An identity’s naming attribute has changed. • Move: An identity’s logical location has changed. This usually applies to identities in a hierarchical system. An event of a certain type in one system can result in an event of a different type in the synchronized system. For example, when a Modify event occurs for an identity that does not yet exist in the external system, an Add event is submitted. There is one more type of event that does not represent a change but is a request for information: the Query event. Novell eDirectory issues queries to your application on the Subscriber channel. You can also query eDirectory from scripts on either Subscriber or Publisher channels. Novell eDirectory supports all of the events above. You should make a list of what the result of a particular event in eDirectory will be in your external application. Conversely, you should list what event types can occur in your external application, which event types are relevant and what the result of relevant events should be in the Identity Vault. 5.2 The Connected System Schema File The schema.def file on the connected system is stored in the schema directory under the driver installation directory. It is used to specify the classes and attributes that are available on the system. The schema file is read by the driver shim when the Metadirectory engine requests it. This typically happens at driver startup. The schema file is also used by the Policy Editor to map the schema of the Identity Vault to the schema of the external application. If you change the schema file, you must restart the driver shim and the driver. The scripts written for the driver depend on the classes and attributes in the schema file. 5.2.1 Schema File Syntax Each line in the schema file represents an element and must begin with the element name: SCHEMA, CLASS, or ATTRIBUTE. The first element of the schema file is the schema definition. The schema definition is followed by class definitions. Each class definition can contain attribute definitions. Except for the values of class and attribute names, the contents of the schema file are case insensitive. Comments Lines that begin with an octothorpe (#) are comments. # This is a comment. 38 Identity Manager 4.0.1 Driver for Scripting Implementation Guide
Schema Definition The first line in the schema file that is not a comment must be the schema definition. SCHEMA [HIERARCHICAL] HIERARCHICAL specifies that the target application is not a flat set of users and groups, but is organized by hierarchical components, such as a directory-based container object. Class Definition CLASS className [CONTAINER] You must specify a class name. Enclose the class name in double quotes ("). Add the CONTAINER keyword if objects of this class can contain other objects. The class definition is ended by another class definition or by the end of the file. Attribute Definition Any number of attribute definitions can follow a class definition. Attribute definitions define attributes for the class whose definition they follow. ATTRIBUTE attributeName [TypeAndProperties] An attribute name is required. Enclose the attribute name in double quotes ("). If no attribute type is specified, the attribute has the string type. The allowable types are: • STRING • INTEGER • STATE • DN The allowable attribute properties are: • REQUIRED • NAMING • MULTIVALUED • CASESENSITIVE • READONLY Example Schema File SCHEMA HIERARCHICAL CLASS "User" ATTRIBUTE "cn" NAMING REQUIRED ATTRIBUTE "Group Membership" MULTIVALUED DN CLASS "Group" ATTRIBUTE "cn" NAMING REQUIRED ATTRIBUTE "Group Members" MULTIVALUED DN Customizing the Scripting Driver 39
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 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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?