Dear Community, we want to synchronize person records from our current Novell eDirectory. The person class is built with the inetorgperson and company related attributes are added with an auxiliary class. After the creation of the MA (and yes, I select all attributes including those from the auxiliary class) I want to create sync rules in FIM. I select the inetOrgPerson class there, but I can only sync attributes from this class and not from the auxiliary class... Any suggestions? Have a nice weekend! Rainer

____ Hugo, I have exactly the same behaviour with SunOne Directory. As you describe, even if you check the attribute from the MA configuration wizard, they are not listed from the dropbox in the Sync Rule creation form. The dropbox only list the attributes from the selected class and not those from auxilliary classes. The fact is that in ObjectType tab from MA configuration wizard, you can see only the structural classes. So you cannot add auxiliary classes to scope in the secret hope that can help FIM to see the attributes from the portal. I think this is directly link to the Management Agent, because in case of Active Directory Management Agent we are able to add ExtensionAttribute1...15 in Sync Rule for exemple. Theses attributes are from an auxilliary class too, bring by the Exchange schema extension. From today, I don't have any workaround to avoid this, except perhaps to use the OpenLdap XMA agent, but this is not a good scenario. Fabrice

Well, I have found a way to managed those invisible attributes coming from auxilliary classes. Even if they are not listed in the FIM portal, they are part of the Connector Space schema, and if the auxilliary classes is instatiate for a person, so they attributes are correctly imported in the CS of the MA. So the real problem here is to be able to flow them into the MV, after that they can be synchronised into the portal if needed. It seems that the only way to do that is to use Extension Rules. I added an attribute flow from the MA configuration wizard and write the following code for the attribute I want to flow: vovoid IMASynchronization.MapAttributesForImport (string FlowRuleName, CSEntry csentry, MVEntry mventry) { switch (FlowRuleName) { case "cd.person:w2kuser->mv.person:services": { if (csentry["w2kuser"].IsPresent) { mventry["services"].Values.Add("w2kusers"); } break; } default: { throw new EntryPointNotImplementedException(); } } } As you can see the goal here is too add an entry in multivalues attribute "service", one of this possible service is "w2kuser" Hope it can help you Fabrice

Hi There, As I'm expecting that the operations of the MA's for Sun/Novell will perform similarly, I have managed the auxilliary object classes within the Sun Directory by adding the requirements in the provisioning code (MVExtension). The code performs the following tasks: 1. Checks to see if a connector exists. (Which when using declarative rules to provision the users, this test passes as true during the first test and creation as the declarative rule connector is committed BEFORE the MVExtension code is run). 2. If the connector exists, add the appropriate auxilliary object classes to the new connector space object. 3. Use normal attribute flow to manage the attributes that are included with the auxilliary object classes. Thanks B