Versions Compared

Key

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

Downstream systems are identity-aware systems that acquire data from EmpowerID regarding the changes in the identity of a person. By connecting to the downstream system you can flow the data of role changes, status changes, terminations, and policy changes in EmpowerID. This helps you manage the identity lifecycle in external systems by just managing the identity of the Person in EmpowerID. Downstream systems can be connected using connectors to transfer data to/from other's identity-aware systems and applications. A simple example of the use case would be when you have group/role membership changes of a person in EmpowerID, you would want that change to be reflected on a connected Active Directory.

To connect EmpowerID to a downstream system, you create an account store object in EmpowerID for that system and then configure the account store for how you want EmpowerID to manage the identity information in that system. Important aspects regarding the flow of data into downstream systems like inventory processing, provisioning and join logic, group membership assignments, naming conventions, and decisions regarding deleting or disabling accounts are handled through the system's workflows in EmpowerID. You have already explored that Attribute Flow rules can be configured, which would trigger the changes into downstream systems whenever there is a change in attributes of the Person object in EmpowerID.

Such user directories and resource systems can be managed and synchronized using Scheduled Connector Jobs. These jobs read current state data from the target systems and reconcile it with the data in the identity warehouse to maintain synchronization with the external system.

In this section, we will learn two important connectors for the Downstream Systems,

  1. Active Directory: Out-of-the-box connector for Microsoft Active Directory that inventories and performs CRUD (Create, Update, Delete) operations for the user, contact, group, user/group assignments, and Organizational Unit objects in the domain.

  2. Azure Active Directory: Azure Active Directory connector is a SCIM-compliant REST API microservice that you can deploy to Azure Active Directory to inventory user, group, group membership, role, and license information from an Azure tenant.

Easy html macro
theme{"label":"solarized_dark","value":"solarized_dark"}
contentByMode{"html":"<!doctype html>\r\n<head>\r\n<link href=\"https://cdn.jsdelivr.net/npm/bootstrap@5.1.0/dist/css/bootstrap.min.css\" rel=\"stylesheet\" integrity=\"sha384-KyZXEAg3QhqLMpG8r+8fhAXLRk2vvoC2f3B09zVXn8CA5QIVfZOJ3BCsw2P0p/We\" crossorigin=\"anonymous\">\r\n</head>\r\n<nav aria-label=\"...\">\r\n <ul class=\"pagination justify-content-center\">\r\n <li class=\"page-item\">\r\n <a class=\"page-link\" href=\"https://dotnetworkflow.jira.com/wiki/spaces/EIDIGACore/pages/2387741231/Universal+Connector\" target=\"_top\"> &laquo; &nbsp;&nbsp;Previous</a>\r\n </li>\r\n <li class=\"page-item active\" aria-current=\"page\">\r\n <span class=\"page-link\">Current</span>\r\n </li>\r\n <li class=\"page-item\">\r\n <a class=\"page-link\" href=\"https://dotnetworkflow.jira.com/wiki/spaces/EIDIGACore/pages/2387741263/Active+Directory\" target=\"_top\"> Next&nbsp;&nbsp; &raquo;</a>\r\n </li>\r\n </ul>\r\n</nav>","javascript":"","css":""}

Insert excerpt
IL:External Stylesheet
IL:External Stylesheet
nopaneltrue