| Note that this HelloID connector has not been tested in a production environment! |
| ℹ️ 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. |
HelloID-Conn-Prov-Target-MyDMS is a target connector. MyDMS provides a set of REST API's that allow you to programmatically interact with it's data. The connector contains Account and Authorization management.
The following settings are required to connect to the API.
| Setting | Description | Mandatory |
|---|---|---|
| UserName | The UserName to connect to the API | Yes |
| Password | The Password to connect to the API | Yes |
| BaseUrl | The URL to the API | Yes |
- At the moment of writing. The response of the permissions (Groups) contains invalid data. I've added a temporary fix to remove the invalid data from the response, so the connector works as intended. Make sure you test your response while implementing the connector.
- Only the connection settings are required
- There are no enable and disable scripts because the _startEmployment is required when creating a user. And the account will be disabled in the delete action, with putting an Enddate (Get-date) - one day) on the user.
- _startEmployment must always be a valid date (dd-mm-yyyy). This will activate the user account on or after that date.
- _endEmployment can be passed either empty (=account is active) or as a valid end date (dd-mm-yyyy). This will deactivate the account after that date.
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/