Sign in
 
HomeLibraryLearnDownloadsSupportForums
Resources for IT Professionals > Forums Home > Identity Management Forums > Identity Lifecycle Manager 2 > Custom Attributes bound to a user/person not availabe in Sync Rule or in ILM MA
Ask a questionAsk a question
Search Forums:
 

AnswerCustom Attributes bound to a user/person not availabe in Sync Rule or in ILM MA

  • Wednesday, June 24, 2009 4:30 PMKevin Korb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hello

    I have added a few custom attributes, bound them to the user object, and added them to the object visualization for users. The new attributes are not available to select in the sync rule or attribute flow in the MA to the ILM. The strange this is when I import a new user from the portal with a value in the custom attribute and search the connector space they are present. Any ideas on what I'm missing. I'm sure it’s something simple

    Thanks

     

Answers

  • Monday, June 29, 2009 3:03 PMKevin Korb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    1
    Sign In to Vote

    Thanks for everyones help

    I just figured it out. As I mentioned I'm new two ILM 2 :)

    I just realized that the attributes listed for flow in the sync rule are not the attributes bound tho that object in the ILM portal rather the attributes defined on the flow from MA to the ILM db. I had to create the custom attribute in the metaverse also, then set the MA to flow that info before it was availabe in the sync rule. Sorry for the elementary question, all your responses helped me figure it out.


    Thanks

     

All Replies

  • Wednesday, June 24, 2009 5:36 PMMarkus VilcinskasMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Have you tried refreshing the schema yet?
    Also, try to see whether exporting the MA changes anything.

    Cheers,
    Markus
    Markus Vilcinskas, Technical Content Developer, Microsoft Corporation
     
  • Thursday, June 25, 2009 3:44 PMKevin Korb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Markus

    Thanks for the rely. I have already refreshed the schema and the attribute is still not avilabe in the sync rule of the ma
     
  • Thursday, June 25, 2009 3:48 PMPaolo Tedesco Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Have you update the list of attributes handled by the agent?
    Select the agent -> Select Attributes -> check "Show All" -> Check the new attributes you created.
    At that point you should be able to see them in the "Configure Attribute Flow" section.

    Cheers,
    Paolo
     
  • Friday, June 26, 2009 3:18 PMKevin Korb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Paolo

    Thanks. After selecting it as an sttribute in the ILM MA  I can see it as a field to be used for flow with the MA. But it is still not selectibale option in the sync rules on the portal. Ayn other ideas ?

    Thanks
     
  • Sunday, June 28, 2009 2:27 AMJef Kazimer Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Paolo,

    I believe you have to do it in this order:

    1 -  Portal-Add the Attribute in the Portal
    2 -  Portal-Add a Binding to the Object for the attribute
    3 -  SyncServer-Refresh Schema on ILM MA
    4 -  SyncServer-Add the Attribute to the Object in the Metaverse Designer

    You will now be able to select the MV attribute in Sync flows.

    I too thought adding it to the Portal would also add it to the MV, but this does not appear to be the case.

    Jef
     
  • Sunday, June 28, 2009 2:06 PMKevin Korb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks Jef

    I can sse the attribute in the MV. My issue is its not visible when setting up the Sync rules in the portal. None of the three custom attributes I created are. I must be missing something simple

    Kevin
     
  • Sunday, June 28, 2009 3:59 PMMarkus VilcinskasMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Kevin,

    have you tried exporting the MA?
    Another option is to add an "artificial" change to the affected MA.
    You could, for example, add another IAF flow rule to your FIM MA.

    The MA data you see in the dialog to configure synchronization rules is replicated from the synchronization service to the portal.
    I have seen cases, where the data was not automatically replicated, which made it necessary to trigger replication.

    Cheers,
    Markus


     
    Markus Vilcinskas, Technical Content Developer, Microsoft Corporation
     
  • Monday, June 29, 2009 2:14 PMKevin Korb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Markus

    Thanks for your response, I knew to ILM 2 and could be missing something. I'm not quite sure if this is related to the MA. I have added a custom binding to the user ubject in the ILM 2 portal. That binding does no appear as an attribute in the "outbound attribute flow" of the sync rule in the portal, but does appear in the MA. The problem is that I'm trying to use the attribute to concatenate another attribute during the provisioning to anotehr conector space with the codeless option in the portal. Thats why I cannot use the attribute in the MA. Hope that makes sense. I must be just missing a simple step. I had this working a few months ago on our test box

    Thanks
     
  • Monday, June 29, 2009 3:03 PMKevin Korb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    1
    Sign In to Vote

    Thanks for everyones help

    I just figured it out. As I mentioned I'm new two ILM 2 :)

    I just realized that the attributes listed for flow in the sync rule are not the attributes bound tho that object in the ILM portal rather the attributes defined on the flow from MA to the ILM db. I had to create the custom attribute in the metaverse also, then set the MA to flow that info before it was availabe in the sync rule. Sorry for the elementary question, all your responses helped me figure it out.


    Thanks

     
  • Friday, July 03, 2009 8:22 PMJoe Stepongzi - ILM MVPMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Kevin,

    When you refreshed the schema on the ILM MA, when you go into the configuration for the ILM MA in Identity Manager.
    You should now see the attribute, you then need to create an attribute flow to the new metaverse attribute that you created.

    Now when you go into the sync rule configuration you should see the metaverse attribute, you will be able to use this attribute in any time of rule.

    Remember, The sync rule configurations only work going from a data source to the metaverse and from the metaverse to the data source.  Any flows from the ILM ma need to be configured in the ma, requiring a schema update and an attribute flow.


    Does this help?

    Joe Stepongzi - Identity Management Consultant - ILM MVP - www.microsoftIdM.com,ilmXframework.codeplex.com