HaloPSA (And other MCP Integrations) need User-based OAuth
under review
C
Chris Green
HaloPSA does not provide a method for users to create their own API keys. HaloPSA intends for user-based MCP access to be done via OAuth as the user. They do support API keys as a beta feature, but they do not provide any ability for users to create their own keys. This means that an Admin would need to create (and maintain) API keys for each user.
This needs to be updated to support OAuth.
J
Julia Carroll
updated the status to
under review
S
Sean Garland
You can add CIPP MCP to the list of ones that don't work... It supports standard OAth2.0 but Hatz says the information is not available. This is super important for us to pull info from CIPP.
S
Sean Garland
This is critical - two separate integrations I tried within the last 3 days required OAuth that Hatz didn't support. Hudu was one, and CData was another.
C
Chris
This is far more important now that Hudu requires the same. :)