Important
This repository contains the connector and configuration code only. The implementer is responsible to acquire the connection details such as username, password, certificate, etc. You might even need to sign a contract or agreement with the supplier before implementing this connector. Please contact the client's application manager to coordinate the connector requirements.
Note
This connector must be used in conjunction with the HelloID-Conn-Prov-Target-Authorizationbox connector.
- HelloID-Conn-Prov-Target-DynamicsEmpire
HelloID-Conn-Prov-Target-DynamicsEmpire is a target connector. DynamicsEmpire provides a set of PowerShell functions allowing you to programmatically interact with its data.
The following features are available:
| Feature | Supported | Actions | Remarks |
|---|---|---|---|
| Account Lifecycle | ✅ | Create, Correlate | Correlation is mandatory. |
| Permissions | ❌ | - | |
| Resources | ❌ | - | |
| Entitlement Import: Accounts | ❌ | - | |
| Entitlement Import: Permissions | ❌ | - | |
| Governance Reconciliation Resolutions | ❌ | - |
Governance Reconciliation Resolutions are not yet available.
URL of the icon used for the HelloID Provisioning target system.
https://raw.githubusercontent.com/Tools4everBV/HelloID-Conn-Prov-Target-DynamicsEmpire/refs/heads/main/Icon.png
- Service account for the HelloID Agent with sufficient rights within Empire to create accounts.
- Service account for the HelloID Agent must be able to connect to the instance where Empire is installed.
- Linked usage with AuthorizationBox connector
The following settings are required to connect to DynamicsEmpire.
| Setting | Description | Mandatory |
|---|---|---|
| PSModulePath | Full path to the NavAdminTools.ps1 file |
Yes |
| Applicationserver | Name of the Dynamics NAV application server | Yes |
| NavServerInstanceName | Name of the Dynamics NAV server instance | Yes |
| Tenant | ID of the Dynamics NAV tenant | Yes |
The correlation configuration specifies which properties will be used to match an existing Empire account to a person in HelloID.
| Setting | Value |
|---|---|
| Enable correlation | True |
| Person correlation field | sAMAccountname |
| Account correlation field | Username |
Tip
For more information on correlation, please refer to our correlation documentation pages.
The field mapping can be imported by using the fieldMapping.json file.
The account reference is populated with the property userSecurityID, FullName & Username from Empire.
It is advised not to change the reference after creation or correlation due to issues in Authorizationbox when changing those fields.
- Service user that runs the agent must have sufficient rights within Empire to create and correlate accounts.
- This connector is usually linked to the AuthorizationBox connector, as Security ID is required there.
The NavAdminTools.ps1 file is dotsourced in all lifecycle actions. Functions defined within the file are imported into the current session. The original code was based on a PSSession with Import-Module and Invoke-Command. Since the file is not a module, this seems unnecessary but requires further testing.
# Import module
$Import = Invoke-Command -Session $s -ScriptBlock {
param($ImportPath)
Import-Module $ImportPath -ErrorAction Stop
} -ArgumentList $PSPathThis connector interacts with DynamicsEmpire via PowerShell functions from NavAdminTools.ps1 rather than REST endpoints.
Tip
For more information on configuring HelloID PowerShell connectors, refer to our documentation: https://docs.helloid.com/en/provisioning/target-systems/powershell-v2-target-systems.html
The official HelloID documentation can be found at: https://docs.helloid.com/
