none
New attribute not visible RRS feed

  • Question

  • I added a new attribute to FIM, bound it to the User resource, did a schema update on the FIM MA but the new resource is not visible to the admin user if I try to use it in an inbound attribute flow. What am I missing. Do I need to add this new attribute to an existing MPR and if so, which one?

    Thanks JD

    Monday, December 1, 2014 3:03 AM

Answers

  • Should have added that to my original post but I did that already.
    Attribute will not show as an attribute for the metaverse object type 'person'.

    If you have extended the FIM Portal/Service User Object schema, than you definitely will not see this attribute in the Metaverse Person Object schema. If you want a new attribuute in the MV, then you need to extend the MV schema.
    • Marked as answer by JOTdude Tuesday, December 2, 2014 4:44 AM
    Tuesday, December 2, 2014 3:05 AM

All replies

  • Make sure you select your new attribute in your FIM MA, under 'Select Attributes'

    Monday, December 1, 2014 3:18 AM
  • Should have added that to my original post but I did that already.
    Attribute will not show as an attribute for the metaverse object type 'person'.
    • Edited by JOTdude Monday, December 1, 2014 4:26 AM
    Monday, December 1, 2014 4:24 AM
  • Please clarify where did you create the new attribute? In the MV Schema or Service/Portal Schema?
    Monday, December 1, 2014 5:44 AM
  • I added a new attribute to FIM, bound it to the User resource, did a schema update on the FIM MA but the new resource is not visible to the admin user if I try to use it in an inbound attribute flow. What am I missing. Do I need to add this new attribute to an existing MPR and if so, which one?

    Thanks JD

    There is a MPR named "Synchronization: Synchronization account controls users it synchronizes". Please make sure you have this attribute selected in "Target Resources" of this MPR either in "All attributes" or in "Select specific attributes".

    Or, for import only (if you don't want to update this attribute based on MV value), check MPR "Synchronization: Synchronization account can read users it synchronizes"

    Also make sure that you use the same service account as specified during installation as FIM MA.


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    Monday, December 1, 2014 6:47 AM
  • @Shim: it was created in the Service/Portal Schema.

    @Dominik: The MPR "Synchronization: Synchronization account can read users it synchronizes" was already set to All People/All Attributes.

    Added the attribute to MPR "Synchronization: Synchronization account controls users it synchronizes" but no difference.

    If I go into the Inbound syncrule, the attribute is not visible in the "destination" drop down list.

    Monday, December 1, 2014 11:33 PM
  • So, in the FIM MA:

    • under 'Select Attributes' you can see your new attribute and have selected it?
    • then if you go to 'Configure Attribute Flow', expand 'Object Type: Person / Data Source Attribute' (NOT 'Metaverse attribute') - do you see your new attribute?
    • If not, did you bind the new attribute to the correct object class in the Portal?


    • Edited by Shim Kwan Tuesday, December 2, 2014 3:03 AM
    • Marked as answer by JOTdude Tuesday, December 2, 2014 4:44 AM
    • Unmarked as answer by JOTdude Tuesday, December 2, 2014 4:44 AM
    Tuesday, December 2, 2014 2:03 AM
  • Should have added that to my original post but I did that already.
    Attribute will not show as an attribute for the metaverse object type 'person'.

    If you have extended the FIM Portal/Service User Object schema, than you definitely will not see this attribute in the Metaverse Person Object schema. If you want a new attribuute in the MV, then you need to extend the MV schema.
    • Marked as answer by JOTdude Tuesday, December 2, 2014 4:44 AM
    Tuesday, December 2, 2014 3:05 AM
  • So, in the FIM MA:

    • under 'Select Attributes' you can see your new attribute and have selected it?
    • then if you go to 'Configure Attribute Flow', expand 'Object Type: Person / Data Source Attribute' (NOT 'Metaverse attribute') - do you see your new attribute?
    • If not, did you bind the new attribute to the correct object class in the Portal?



    Thanks Shim, all the above questions are "Yes".

    Anyway, in the meantime I have applied your next reply.
    I was under the impression that both schema's were the same but I have now removed the original attribute and bindings from the portal schema and added the attribute in the MV using the sync engine gui. That worked. Thanks

    Tuesday, December 2, 2014 4:44 AM
  • So, in the FIM MA:

    • under 'Select Attributes' you can see your new attribute and have selected it?
    • then if you go to 'Configure Attribute Flow', expand 'Object Type: Person / Data Source Attribute' (NOT 'Metaverse attribute') - do you see your new attribute?
    • If not, did you bind the new attribute to the correct object class in the Portal?

    Thanks Shim, all the above questions are "Yes".

    Anyway, in the meantime I have applied your next reply.
    I was under the impression that both schema's were the same but I have now removed the original attribute and bindings from the portal schema and added the attribute in the MV using the sync engine gui. That worked. Thanks


    Tuesday, December 2, 2014 4:46 AM