| Note that this connector is "a work in progress" and could require some work to get ready for production environments. Read-me is outdated and still needs to be updated. |
| ℹ️ Information |
|---|
| 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. |
| ℹ️ Information |
|---|
| This connector must be used in conjunction with the HelloID-Conn-Prov-Target-DynamicsEmpire connector |
HelloID-Conn-Prov-Target-Authorizationbox is a target connector. Authorizationbox provides a set of REST API's that allow you to programmatically interact with its data. The connector correlates and updates the user.
The following lifecycle events are available:
| Event | Description | Notes |
|---|---|---|
| create.ps1 | Update and correlate an Account | - |
| update.ps1 | Update the Account | - |
| entitlements.ps1 | Updates all entitlements | - |
The following settings are required to connect to the API.
| Setting | Description | Mandatory |
|---|---|---|
| UserName | The UserName to connect to the API | Yes |
| Token | The Token to connect to the API | Yes |
| Database | The Database where the users are stored | Yes |
| BaseUrl | The URL to the API | Yes |
| Application server information | Information containing information about the applicationserver such as instance name, powershell module path, but also dynamics tentant, permissions and languageID | Yes |
This connector requires specific configuration. Requirements are as followed: Permissions can only be set through SubPermissions. Because Authorizationbox works with 'requests' that can be denied, HelloID must always check which permissions have been assigned to a user before setting up a request. Doing so, makes whatever is calculated by HelloID contracts 'the truth. Additional roles can not be set by hand, as these will appear in a 'remove' request every time the permissions is updated.
Because Authorizationbox only accepts requests that can be denied or approved, HelloID can not set permissions through Business Rules. Monitoring requests status can not be done through HelloID and this will lead to mismatched.
Only 1 request can be open at any time. There is example code added for updating authorization requests, but this does not work. Instead, we delete the old request and build a new one.
Organizational Units must be named exactly as in the source system
Functions must be named exactly as in the source system
If a combination can not be found, this connector will generate an error
Users will currently not be created in AuthorizationBox. Instead this script creates or correlates a user account in Microsoft Dynamics 365 Business Central. It checks if the user already exists (correlates) or creates a new user, configuring necessary attributes like username, email, and permissions. Currently we do not compare the user, and will always update when a user is correlated.
This connector users the nav-tools powershell scripts that Business Central supplies.
Be aware that this might have unexpected implications.
How to setup the connector in HelloID. Are special settings required. Like the primary manager settings for a source connector.
For more information on how to configure a HelloID PowerShell connector, please refer to our documentation pages
If you need help, feel free to ask questions on our forum
The official HelloID documentation can be found at: https://docs.helloid.com/