Containers and XML UMI container names

When data is requested from a resource manager, the granularity of the returned XML data is at the level of a single container of information. The container is normally also the smallest data element. For example, elements that might be considered for billing purposes.

This convention also applies to the UMI XML model. The UMI used in user mapping rules is also defined and manipulated as containers of XML data. For example, the stsuuser:STSUniversalUser XML object that is defined in XML user mapping model is an example of a UMI container.

The topmost element in the definition of an item of UMI is the container name of that item. When we define an authenticated user mapping rule, the XPath to the XML definition of data in any UMI container must be referenced with the name of the container as the first element after /XMLUMI.

To access any element in the stsuuser:STSUniversalUser container in the UMI item stsuuser:STSUniversalUser example, prefix the XPath specification with stsuuser:STSUniversalUser. For example, "/stsuuser:STSUniversalUser/stsuuser:AttributeList/stsuuser:Attribute[@name='username']/stsuuser:Value" refers to the username value.

To access this information from an authenticated user mapping rule, prefix this XPath with the top-level element of the XML target UMI input document, which is XMLUMI. For example, "/XMLUMI/stsuuser:STSUniversalUser/stsuuser:AttributeList/stsuuser:Attribute[@name='username']/stsuuser:Value".

The example rule file contains a template match statement of /XMLUMI/stsuuser:STSUniversalUser/stsuuser:AttributeList, which means that we can specify all attributes of the user mapping file without a prefix. For example, "/XMLUMI/stsuuser:STSUniversalUser/stsuuser:AttributeList/stsuuser:Attribute[@name='username']/stsuuser:Value" is the same as "stsuuser:Attribute[@name='username']/stsuuser:Value". For more information, see Format and constraints of rules.

Parent topic: Authenticated User Mapping