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 password strength validation rules is also defined and manipulated as containers of XML data. For example, the stsuuser:STSUniversalUser XML object that is defined in XML password strength validation 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 a password strength validation 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='password']/stsuuser:Value" refers to the password value.

To access this information from a password strength validation 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='password']/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 password strength validation file without a prefix. For example, "/XMLUMI/stsuuser:STSUniversalUser/stsuuser:AttributeList/stsuuser:Attribute[@name='password']/stsuuser:Value" is the same as "stsuuser:Attribute[@name='password']/stsuuser:Value". For information, see Format and constraints of rules.

Parent topic: Password strength