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

Experience writing a Java based DirXML Driver

Based on the customer project, I wrote a DirXML driver which provision users through Novell Identity Manager 3.5.1 to their company intranet portal ( A Plone System). The portal exposed the RESTful API interfaces. So I started looking first at the Novell SOAP driver to see if it fit our needs. But while reading the driver documentation i felt it required too much XSLT knowledge + more customization and testing on the driver. And again it used the Apache HttpClient, Which is more a HttpClient rather then it targets to any specific protocol implementation. So If you could build SOAP messages at your own so it would help you in transporting these message back and forth between IDM and Application. The Novell SOAP driver comes up with two built in configurations "SPML and DSML", but in my case none of them were suitable. I had always wished to write my own DirXML driver at my own, so I thought why not just take this opportunity to fulfill my wish and at the same time get s...
1 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