To provide ISC users with stronger product integrations as part of our new Unified Platform Access Program, admins must now specify the approved integration when creating an API or Personal Access Token to install it. This change enables deeper integrations and will allow admins to better view traffic related to those integrations in the future.
What constitutes an “approved integration”? Is there some kind of vetting process before a PAT can be used? Does this impact our workflow for generating PATs for Workflows, scripts, or external API integrations?
It seems if I would go look first, I might’ve answered my own question. It looks like, for now at least, y’all allow an override to the required field where we can check the “Other / No associated vendor integration” box.
Hi Mark. Right now, it doesn’t change much. This release is to support our improved partner program, and it had to be released to enable new integrations from our partners. We should see some announcements on the new integrations soon. But this also lets us provide visibility for admins on the traffic being generated by those integrations, and we hope to have those widgets available by end of the year.
Perhaps the title “Enhancement: Support for Stronger Integrations” is a bit vague/ambiguous, also taking into account when the conclusion is “Right now, it doesn’t change much.”
I am a bit concerned for that upcoming changes. Have you done a In discovery round, or do you plan to organize one? I have not found one at least and I am happy to give my feedback.
Note that I found this announcement by changing a PAT, seeing this field. Looking into the documentation for this and seeing it was not mentioned. Only then, I searched for and found it here.