The UXP Identity Object contains integral components, or artifacts, that embed in the UXP Object. These artifacts include User Definitions, which are the permitted users, and policies. Together, these artifacts participate in generating the unique UXP Protection Scheme within a UXP Object. Therefore, the UXP Identity precedes the UXP Object.

UXP Identity Construction Components

The UXP Identity construction requires:

  • Owner-Defined Artifacts
    • Public attributes
      • Name
      • Address (optional)
      • Phone  (optional)
      • UXP internal metadata (these attributes are UXP Technology generated automatically)
    • Private attributes
      • User Definition(s) – the listed permitted Users (User Credential) for access to a UXP Object
      • Policies
      • Configurations(s) (optional)
  • UXP Technology Components

Owner-Defined Artifacts

These artifacts are a combination of owner-defined and UXP Technology-generated attributes.

As noted, two types of attributes exist:

  • Public
  • Private

Public Attributes

The public attributes are mixed set of details. Some attributes are automatically generated; other attributes are supplied by the UXP Identity owner/creator. Not all owner-supplied attributes are required.

After the UXP Identity is active and saved as a *.iic file, the public attributes can be seen on the OS as a pop-up. To see the pop-up, the *.iic file needs to be proximal to UXP Technology. Clicking the file opens the pop-up. This pop-up is called the ID Content page, Figure 2 below.

These public details include:

Private Attributes

The private attributes include:

  • User Definitions
  • Policies
  • Configurations

User Definitions: User Definitions are embedded in the Identity and designated by the Identity owner.

A User Definition includes:

  • Valid User (machine, process, human, or any combination)
    • Challenge Pairs
      • Prompt
      • Response

  • Optional device and location configurations, user specific

Policies: Policies are specific access and mitigation protocols defined by the data owner. Both access and mitigation policies center around behaviors designed to protect the UXP Object and its data.

Policies are referred to as rule presets in throughout UXP Technology documentation. More specific information on the rule presets, see the Workflow Guide/Section 3.1.2 Rule Presets

Configuration(s): A configuration in the context of a UXP Identity refers to defining specific parameters for where data access is permitted. These include two types of information noted below:

  • Network location
  • Hardware / device

A configuration uses both information types to create a unique fingerprint using the device and location that locks down where data is accessed.