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 - 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

Novell IdM 3.6 : Creating custom Subscriber PostProcessor Java extension for Delimited Text Driver Part 1

I had chance to write a custom PostProcessor extension for a Delimited Text Driver for Novell Identity Manager,  " t he PostProcessor extension should execute the code under another Windows Domain User account. So I decided to run the driver with Remote Loader Configuration, running the DirXML windows Service under another Windows Domain User Account. " Software and settings in my setup: * Novell Designer 3.0.1 (build  Jan 5, 2009) * Novell Identity Manager 3.6 / Windows Server 2003 R2 * Novell iManager 2.7.2 * Delimited Text Driver 3.6 ver 2.0 (imported configuration  file from Designer 3.0.1) * And the Delimited Text Driver was going to run on the remote server (Remote Loader),  * Java IDE was  (IntelliJIDEA) i started first with digging into documentation of the driver, and i came a cross this section: Using Java Interfaces to Customize File Processing: http://www.novell.com/documentation/idm36drivers/delimited/index.html?page=/documentation/idm36drivers/delimited/data/bkt...
1 comment
Read more