GLPI
The GLPI connector allows data synchronization between GLPI and RAC/M Identity. To do this, the connector uses the GLPI Rest API.
Configuration
The following parameters are required regardless of the authentication method used:
| Configuration | Description |
|---|---|
| API URL | The URL of the API to connect to. |
| Authentication method | The authentication method to use for connecting to the API. Possible values are userToken and password. |
| App token | The token used to connect to an instance of the API client. It can be found in Configuration -> General -> API. |
| Connection Timeout in seconds | Maximum time, in seconds, before a connection attempt is terminated. |
| Page size | Maximum number of items returned per paginated API request. |
Advanced Configuration
| Configuration | Description |
|---|---|
| Timeout | Timeout in milliseconds. |
| Thread Pool Size | The number of threads to be used for concurrent operations. Leave empty to use all available threads. |
| Time between retries | The waiting time before an HTTP request is retried. Leave empty to use 500ms. |
| Custom Config 1 to 5 | Custom configurations that can be used by the script. |
| Username | Username to use for authentication. |
| Password | Password to use for authentication. |
| User Token | User token to use for authentication. |
| Bearer Token | Bearer token to use for authentication. |
| Custom Secret 1 to 5 | Custom secrets that can be used by the script, securely encrypted and managed. |
Information Required for this Connector
This section is empty or incomplete. We will add the information soon. If you have content suggestions, please open a support ticket with your suggestions.
Authentication
Authentication can be done in two ways: with a user token or with a username and password.
Authentication with a user token is the recommended method. It is more secure than authentication with a username and password.
User token
Username and Password
Note: This authentication method is not recommended. If possible, use a user token instead.
Information Required for this Connector
- What is the user's token?
- What is the application's token?
- What is the REST API endpoint?
- Information for Manual Provisioning
- What is the URL of the application's web portal?
- What are the user and groups to whom the tickets will be assigned?
- What is the observer ID? Should they be notified?
- What is the requester ID? Should they be notified?
Configuration as a System for Manual Provisioning Requests
| Configuration | Description | Example |
|---|---|---|
| glpiRestApiUrl | The URL of the GLPI REST API endpoint used to interact with the system. | https://dns/apirest.php |
| glpiUrl | The URL of the GLPI web interface, used for user navigation and access. | https://dns/front |
| glpiAppToken | The application token required for API authentication. | |
| glpiUserToken | The user token required for API authentication, associated with a specific GLPI user. | |
| manualProvisioningAssignees | A semicolon-separated list of user and group IDs for manual assignment during provisioning. | User Id;Group Id |
Information for Manual Provisioning
- What is the URL of the application's web portal?
- What is the user and group to which tickets will be assigned?
- What is the ID of the observer? Should they be notified?
- What is the ID of the requester? Should they be notified?
Manual Provisioning
The Groovy script must be placed in the Manual Provisioning section. Once this new provisioning is created, we will be able to use it in the desired asset.