starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 00:06:06 +03:00

[GH-ISSUE #5392] [Feature Request]: HaloITSM #2601

New issue

Open

opened 2026-03-02 13:53:39 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 13:53:39 +03:00

Owner

Originally created by @blastone-alexander-home on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5392

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

The current integration got HaloPSA does not authenticate with HaloITSM. HaloITSM is a reduced feature set product of PSA, it is primarily used for IT divisions inside companies. This is relevant for users of CIPP who are only managing a single tenant ('Partner Tennant').

Currently we receive the error: Failed to connect: Response status code does not indicate success: 401 (Unauthorized).. Line 16 when try to configure the HaloPSA integration to HaloITSM.

Benefits for MSPs

N/A. This would benefit internal IT divisions who use CIPP.

Value or Importance

Value to us is high. As there is an existing HaloPSA integration, and HaloITSM is PSA with a few features removed (and a different url) the integration for ITSM should be as simple as updating the API url's.

PowerShell Commands (Optional)

No response

Originally created by @blastone-alexander-home on GitHub (Feb 18, 2026). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5392 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement The current integration got HaloPSA does not authenticate with HaloITSM. HaloITSM is a reduced feature set product of PSA, it is primarily used for IT divisions inside companies. This is relevant for users of CIPP who are only managing a single tenant ('Partner Tennant'). Currently we receive the error: `Failed to connect: Response status code does not indicate success: 401 (Unauthorized).. Line 16` when try to configure the HaloPSA integration to HaloITSM. ### Benefits for MSPs N/A. This would benefit internal IT divisions who use CIPP. ### Value or Importance Value to us is high. As there is an existing HaloPSA integration, and HaloITSM is PSA with a few features removed (and a different url) the integration for ITSM *should* be as simple as updating the API url's. ### PowerShell Commands (Optional) _No response_

kerem added the

labels

2026-03-02 13:53:39 +03:00

kerem commented

2026-03-02 13:53:40 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 2, 2026):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

@github-actions[bot] commented on GitHub (Mar 2, 2026): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#2601

No description provided.

Rows
Columns