Page Comparison

One of the key concepts to understanding EmpowerID is its Identity Warehouse, sometimes known as the Identity and Entitlement Warehouse. This The Identity Warehouse is the primary central database of EmpowerID that stores all major primary data, including configuration and policies, major significant EmpowerID objects like Person and Roles, inbox and outbox queues used to stage detected changes and outbound changes between EmpowerID and managed systems, as well as the tables holding the inventoried objects and their data from external managed systems . External external to EmpowerID. EmpowerID refers to these external managed systems are referred to as Account Stores and Resource Systems in EmpowerID terminology.

High-Level Stats for the Identity Warehouse:

• >1,200 tables

• >700 views

• >20,000 stored procedures

It is not essential to learn the specifics of these tables, views, and stored procedures as most are used for internal purposesuse. Key views and stored procedures used by the user interfaces can be identified by hitting pressing F12 in your browser and viewing what is being called on the network tab.

EmpowerID “Components”

When working with EmpowerID or its support staff, a key term you will encounter is the EmpowerID “Components“EmpowerID Components.” The These components are how EmpowerID exposes the Identity Warehouse tables, views, and stored procedures are exposed of the Identity Warehouse for use in the API. All major SQL tables and views are created as programmable objects against which the user interface acts to retrieve and view present their data and , workflows, and code act to create, update, or delete themto allow CRUD operations to be performed. All of the columns in SQL for a table or view become properties of its corresponding programmable component object. Therefore, extending the schema is referred to as extending the components by adding to them new “virtual” properties or methods. We’ll talk about extending the schema in more depth in a later training module.

Although the list of components is extensive, many are disabled by default and not available to show in the user interfaces or be called by custom applications and developers. As a quick illustration, we can see that the Account component, which represents the SQL account table, is not available in the API, while the more secure AccountView component is. To be noted, the schema management user interface labels components as RBAC Objects. This is because there is an entry for every table and view, aka “component” in the RBACObject table, used to display this data. The SQL stored procedures for these components can be seen on the RBAC Object Methods tab.