| ℹ️ 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. |
-
The 'HelloID-Conn-Prov-Target-SDB-Identity' connector is a target connector based on scim based API's. http://www.simplecloud.info.
-
The SDB Identity Platform serves as the central hub for connecting and managing access to underlying applications. More information about the supported applications can be found in the API documentation
The following features are available:
| Feature | Supported | Actions | Remarks |
|---|---|---|---|
| Account Lifecycle | ✅ | Create, Update, Enable, Disable | There is no Delete action, the disable acts as a soft delete |
| Permissions | ✅ | Retrieve, Grant, Revoke | Static or Dynamic |
| Resources | ❌ | - | |
| Entitlement Import: Accounts | ✅ | - | |
| Entitlement Import: Permissions | ✅ | - | |
| Governance Reconciliation Resolutions | ✅ | - |
| Setting | Description |
|---|---|
| ClientID | The ClientID for the SCIM API |
| ClientSecret | The ClientSecret for the SCIM API |
| Uri | The Uri to the SCIM API. http://some-api |
The correlation configuration is used to specify which properties will be used to match an existing account within {connectorName} to a person in HelloID.
| Setting | Value |
|---|---|
| Enable correlation | True |
| Person correlation field | PersonContext.Person.ExternalId |
| Account correlation field | employeeNumber |
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 id property from SDB-Identity
- The employee number may only contain numeric values and no letters.
- Usernames should consist of a single, continuous string without spaces.
- The User object returned by the API differs from the one used in the field mapping. As a result, the create, update, and import actions require duplicate mappings to ensure proper data handling.
Not all SCIM attributes are supported; only the fields listed below are available for use.
- Email: The user's email address (only work email addresses are supported).
- Username: The user's username (must not include spaces).
- Name: The user's full name.
- Active: The user's activation status.
- EmployeeNumber: The user's employee number (numeric values only).
The following endpoints are used by the connector
| Endpoint | Description |
|---|---|
| /Users | Retrieve, Create and Update user information |
| /Groups | Retrieve group information, Add or Remove users |
For more information on how to configure a HelloID PowerShell connector, please refer to our documentation pages
Tip
For more information on how to configure a HelloID PowerShell connector, please refer to our documentation pages.
Tip
If you need help, feel free to ask questions on our forum.
The official HelloID documentation can be found at: https://docs.helloid.com/
