End to end tutorial
The end-to-end tutorial is installed as part of the Omada Connectivity SDK and shows you how to fully manage a directory with users, groups and assignments.
The directory is persisted in the SampleDirectory.xml
file, which you must install, manage and configure. The file path is C:\Program Files\Omada SDK\V14.0\ tutorials\endto-end.
The end-to-end tutorial includes the configuration and code to read and write to a user, as well as a permission repository in an XML file.
All files and code are referenced in the tutorial.sln
file, which you can open using Visual Studio. The tutorial itself is also located in the \end-to-end folder.
This tutorial helps you perform the following procedures:
-
Deploy and register the connectivity in Omada Identity.
infoThe Register Connectivity utility does not work if the SDK version does not match your version of Omada Identity. You must also run the utility on the server where Omada Identity is installed. Alternatively, you must add the following registry key to the Omada Identity database:
HKEY_LOCAL_MACHINE\SOFTWARE\Omada\Omada Enterprise\14.0\ConnStr
-
Write a .NET based query collector for the warehouse, which reads information from the
SampleDirectory.xml
file. -
Write a system onboarding
POST
action that validates input. -
Write a custom Queries and mappings screen.
-
Write a provisioning connector, including data model and task mappings that can update the
SampleDirectory.xml
file.
Overview of folders and files
This table shows the different folders and files in this tutorial:
Name of folder or file | Description |
---|---|
tutorial.sln | This file is the Visual Studio solution file. |
SampleDirectory.xml | This file contains the directory with roles, users and assignments that you want to manage. |
\configuration | This folder contains references to all the files that are necessary for registering the connectivity in Omada Identity. |
\collector | The collector project is a .NET assembly project that implements a query collector for the Omada Data Warehouse and reads data from the SampleDirectory.xml file. |
\connector | The connector project is a .NET assembly that is used by the Omada Identity Provisioning Service to write to the SampleDirectory.xml file. |
\postaction | The POST action project is a .NET assembly which is used by Enterprise Server during system onboarding. The POST action validates connection details. |
Target system
The tutorial provides guidance for end-to-end connectivity for a sample directory. The sample directory contains users, roles and assignments between users and roles. All entities are stored in the SampleDirectory.xml
file. Initially, the content of the file is limited to a list of predetermined roles. See the following code sample:
<?xml version="1.0" encoding="utf-8"?>
<SampleDirectory xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Roles>
<Role>
<Action>C</Action>
<RoleId>0001</RoleId>
<RoleName>ROLEA</RoleName>
</Role>
<Role
<Action>C</Action>
<RoleId>0002</RoleId>
<RoleName>ROLEB</RoleName>
</Role>
</Roles>
</SampleDirectory>
The default import for this project sample is set to Delta in the OnboardingConfiguration.xml
file. This is reflected in the code sample.
The Action field, shown in the above sample code, is mapped from the Queries and Mappings task specified in the onboarding page. This must be completed for a delta import and should specify if the data has been deleted (D) or created/changed (C) in the source system.
Delta import can also be used in combination with the high-water mark functionality. The usage will depend on the source system.
📄️ Step 1 – Manual deployment
In this first set of procedures, you must deploy and register a new connectivity, so it can be used in the system onboarding process.
📄️ Step 2 – Test the connectivity
The next step in the end-to-end tutorial is to test your connectivity and see where each of the deployed and registered components comes into play.
📄️ Step 3 – Writing the collector
A Query collector allows you to write a fully customized collector without the need to dive to deep into technical aspects of SSIS or deploy custom packages.
📄️ Step 4 – Writing the connector
To perform provisioning, you must write a connector. To do this, you must create a solution in Visual Studio, create a connector configuration class and implement the connector logic.
📄️ Step 5 – Writing the POST action
The system onboarding POST action can be used to verify and modify already-entered onboarding values. In the following example, you can write a POST action, which validates that the entered path to the XML file for the directory is correct, and therefore confirm that the file does exist.