viewOptions.PartialMetaView

I am using IdM 7.1. I have a question about "Partial Loading" of MetaView Information as described in the Technical Deployment manual (quoted next).

Partial Loading of MetaView Information

When Identity Manager populates a User view for Reconciliation, Load from Resource, or

Load from File, you can designate loading only the resource account data from the

resources that are assigned to an Identity Manager user that are also targets sourced from

the resource being loaded (and therefore subject to change). The Identity Manager user's

operational attributes that do not affect accounts for example, account ID and organization

are always in the view, as are user extended attributes such as firstname, and lastname.

I have created a resource adapter (LDAPAccount) and set up the reconciliation policy so that when I run reconciliation it should provision an ldap account if that account is missing.

I was hoping that I can use MetaView attributes to define the required attributes that need to be provisioned in ldap. For example, I have an Identity Attribute called objectclass. I assign it a constant value. I specify "set to value" and I specify the LDAPAccount resource as a target for creates and updates.

The automatically generated User MetaView Form contains this:

<Field name='accounts[LDAPAccount].objectclass'>

<Expansion>

<ref>metaView.objectclass</ref>

</Expansion>

<Disable>

<isTrue>

<ref>viewOptions.PartialMetaView</ref>

</isTrue>

</Disable>

</Field>

I tried debugging this code and viewOptions.PartialMetaView is true so this field is disabled and the constant value that I want to assign to this attribute is not assigned.

Can anyone explain how one controls this viewOptions for the metaview form? When I read that paragraph from the documenation it seems to me that I am reconciling the LDAPAccount resource and that it is also a target for my objectclass Identity Attribute in this case so I would think that PartialMetaView should be false.

[2157 byte] By [alpaca-sweeta] at [2007-11-27 10:57:35]
# 1

Hi alpaca-sweet,

I noticed the same thing a while back.

During a reconciliation, the MetaView system only processes Identity Attributes that come from the resource being reconciled against. All other attributes are disabled, as you noticed in the MetaView's form.

Thus, any attribute whose source is a constant or a rule (ie - not the resource being reconciled) is ignored.

To assign attributes like organizations, roles, etc., that don't come from the resource, you'll need to put those as <Expansion>s in the proxy admin's UserForm (or the per-account workflow, but that's overkill I think if you're just setting attributes).

So like if you want to dynamically assign roles to users as they're created, you can put something like the following into the proxy admin form to complement the identity attributes:<Field name='waveset.roles'>

<Default>

<rule name='Example - Determine User Roles'/>

</Default>

</Field>

Hope that helps,

Adam Ohren

Professional Services

QoS Labs, LLC

aohrena at 2007-7-29 12:10:06 > top of Java-index,Web & Directory Servers,Directory Servers...