Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Although the list of components is very large, many are disabled by default and not available to show in the user interfaces or to 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 their is an entry for every table and view, aka “component” in the RBACObject table which is used to display this data. The SQL stored procedures for these components can be seen on the RBAC Object Methods tab.

Info

Key Takeaways:

  1. EmpowerID is built on what is called an Identity and Entitlement Warehouse

  2. The Identity and Entitlement Warehouse is a highly relational database storing configuration, EmpowerID IAM objects, as well as objects inventoried from external managed systems.

  3. Tables and views are made into programmable objects with an API called components

  4. Views have built in security and data filtering and are therefore what is usually exposed in the user interfaces

  5. Components are also known as RBAC Objects and can be made accessible or inaccessible via API by checking a checkbox.