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

Popular posts from this blog

My own developed - Active Directory Cache Inspector for AD Driver Novell Identity manager

Sometimes there is a need for us (Consultants) to see a snapshot of all the changes that happened on the Active directory side while the Novell AD IDM driver was stopped or was not running, before we decide to start the AD driver. Since Novell Identity Manager currently allows us to see all the events which happened in the Identity vault only, but not on the AD side, I decided to write such a tool myself, and of course wanted to share this tool with the consultants/community out there. It's a .NET 2.0 WinForm application, written in C# programming language. To run this tool you should have at minimum: .NET 2.0 framework installed, ( Not supported on the Linux platforms yet) This application must be run under the same user which is configured on the AD driver. Short Tutorial (How To): When you run the application (ADCView.exe), the application automatically discovers the current domain, a domain controller, and default domain naming context in the user logged in domain automatically

NetIQ IDM - How to read Component type data from Query nodeset done from command transformation

Suppose query: <do-set-local-variable name="local.sub.ctp.QueryContacts" scope="policy"> <arg-node-set> <token-query class-name="User" scope="entry"> <arg-match-attr name="UPN"> <arg-value type="string"> <token-src-attr class-name="User" name="UPN"/> </arg-value> </arg-match-attr> <arg-match-attr name="contacts"> <arg-value type="string"> <token-text xml:space="preserve">get-contacts</token-text> </arg-value> </arg-match-attr> <arg-match-attr name="userid"> <arg-value type="string"> <token-association/> </arg-value> </arg-match-attr> </token-query> </arg-node-set> </do-set-local-variable> Outpu