Sun Identity Manager Deployment Reference


Like all views, the user view is implemented as a GenericObject that contains a set of attributes. The values of the attributes in the root object are themselves GenericObjects. Attributes can be nested.

The user view contains the attributes described in the following table, which are further defined in subsequent sections.

Table 3–1 Top-Level Attributes User View




Contains information stored in the Identity Manager repository (the WSUser object). This is sometimes referred to as the basic view.


Contains the values of all resource account attributes fetched from resources. These are typically the values that are edited with forms. 


Contains read-only information about the resources and accounts associated with the user. 


Contains the read-only runtime state for the interface. It is used only during interactive editing of the user. display.session describes login and access information. display.subject identifies the account under which the user is logged in. display.eventType indicates whether the user view is servicing a create or an update operation.


Contains attributes that are synchronized across all resource accounts. 


Contains attribute values that are specific to the user’s password, password expiration, and target systems. 

When you design a form, the field names are typically paths into the user view objects waveset. global, and account attributes (for example, global.firstname).

Selecting the Appropriate Variable Namespaces

The user view provides several namespaces for deriving account-related information. The following table summarizes these variable namespaces.

Table 3–2 Account-Related User View Attributes

Account-Related Namespace 



Used internally for difference detection during check-in operations. It contains the starting values for all account attributes. Do not modify this value. 


Derived read-only information about the accounts that are linked to the user and their associated resources. Use this attribute in forms, but do not modify. 


Stores the read/write copies of the account attributes. Updatable fields should point to this namespace. 


Stores copies of global attributes. Values in this area appear only if the form defines global fields, or if you are using the special MissingFields reference. (The form determines how global attributes are processed.) 

If you set a global attribute in a workflow, you must also define a global field in the form. Simply depositing a global value in the view is insufficient.