Skip to main content

FIM2010 And Novell eDirectory 8.8 SP3 (20216.80)

Okk... finally I have now installed FIM2010 after doing lots of programming excercises on ILM 2007 software..

my first try was to setup a Novell eDirectory Management Agent in FIM2010... uH... It really didn't work...

LDAP traces on the Novell Directory shows that FIM2010 is asking for something here


LDAP : New cleartext connection 0x456d5c0 from FIMIDIOT:21575, monitor = 0x684, index = 1
LDAP : DoBind on connection 0x456d5c0
LDAP : Bind name:**********, version:3, authentication:simple
LDAP : Sending operation result 0:"":"" to connection 0x456d5c0
LDAP : DoSearch on connection 0x456d5c0
LDAP : Search request:
base: ""
scope:0 dereference:0 sizelimit:0 timelimit:0 attrsonly:0
filter: "(objectClass=*)"
attribute: "vendorVersion"
LDAP : Sending search result entry "" to connection 0x456d5c0
LDAP : Sending operation result 0:"":"" to connection 0x456d5c0
LDAP : DoUnbind on connection 0x456d5c0
LDAP : Connection 0x456d5c0 closed


After posting a Bug to the Connect(Beta)... i was told to try following:

Tune your eDirectory server to "Enable old ADSI and Netscape schema output" which is according to iManager is a "Nonstandard Behaviors" :)

And create registry key on your FIM2010 server with following hives

HKLM/System/CurrentControlSet/Services/FIMSynchronizationService/Parameters/eDirectoryMASupportedServers Reg_multi_sz
In the value, add the vendorVersion value obtained, e.g. in my scenario
"LDAP Agent for Novell eDirectory 8.8 SP3 (20216.80)"

WoW!!..finally i got my FIM2010 Management Agent talked to the Novell eDirectory server!!

Comments

Post a Comment

Popular posts from this blog

NetIQ IDM - JDBC statemens using policy builder

Few examples of using JDBC statements using dirxml policies On the Output policy: Handling matching policies with operation-data support: < rule > < description > [DB] Convert Query to DDL doc </ description > < comment name = "author" xml:space = "preserve" > Maqsood Ali Bhatti </ comment > < comment name = "version" xml:space = "preserve" > 5 </ comment > < comment name = "lastchanged" xml:space = "preserve" > Dec 20, 2017 </ comment > < conditions > < and > < if-operation mode = "case" op = "equal" > query </ if-operation > </ and > </ conditions > < actions > < do-append-xml-element expression = ".." name = "jdbc:statement" /> < do-append-xml-element expression = "../jdbc:statement[las...
Post a Comment
Read more

NetIQ IDM - Strip unwanted group member values from current operation

This code example shows how to remove unwanted group members from current operation based on some business logic. Optimization group members add to avoid  "ALREADY_EXIST_VALUE" kind of errors. when IDM engine fails to do so. Here I am doing look up in AD for members, and for each added member from IDM if user is already member of AD group, i am just striping out current member value from the current operaiton. < do-set-local-variable name = "group-dn" scope = "policy" > < arg-string > < token-src-dn /> </ arg-string > </ do-set-local-variable > < do-set-local-variable name = "group-members" scope = "policy" > < arg-node-set > < token-dest-attr class-name = "Group" name = "Member" /> </ arg-node-set > </ do-set-local-variable > < do-trace-message > < arg-string ...
Post a Comment
Read more

NetIQ IDM - Adding operation-data to subscriber command transformaiton custom commands

Recently i had to execute EOL cmdlets using psexecute though new NetIQ azure ad driver, since this operation is fire and forget in nature, i would like to track whole request and response for my own generated commands from subscriber command transofrmaiton policy, so i solved it by following policy: < do-set-dest-attr-value direct = "true" name = "psexecute" > < arg-association > < token-resolve datastore = "src" > < arg-dn > < token-text xml:space = "preserve" > {userref} </ token-text > </ arg-dn > </ token-resolve > </ arg-association > < arg-value type = "string" > < token-local-variable name = "cmdlet" /> </ arg-value > </ do-set-dest-attr-value > < do-append-xml-element expression = "../modify[@direct]" na...
2 comments
Read more