StackJack 0.1.0.12361+687591d
StackJack 0.1.0.12361+687591d
This release adds the Bluechip Infotech connector, Huntress Managed SAT tools, Sign in with Cloudflare, more NinjaOne tools, and a way to authorize your own Microsoft app in all of your GDAP customer tenants at once. It also includes clearer Halo error guidance and fixes for Ingram Micro connection checks and AI Governance scan alerts.
New features
- Bluechip Infotech connector. Connect with your Bluechip EDI username and password. Both fields are required each time you save. The connector includes nine tools:
- Seven read tools, available on the Free plan. This includes freight quotes, which do not book anything.
- Two write tools, available on Pro, to submit and update customer purchase orders.
Test connection reports a wrong username or password as a sign-in problem. An account still in Bluechip's TEST mode is reported as a permissions limitation, not a bad password.
- Huntress Managed SAT. The Huntress connector now also works with Huntress Managed Security Awareness Training and adds 44 Managed SAT tools.
- To use them, add the optional Managed SAT client ID and client secret to your Huntress connection. Leave the fields blank to keep a stored pair.
- Without these credentials, the Managed SAT tools report that they are not configured.
- If Managed SAT rejects the pair, Test connection reports it, but your Huntress connection is not disabled.
- Sign in with Cloudflare. You can now connect Cloudflare by signing in with your Cloudflare account instead of pasting an API token. The organization owner completes the sign-in. API-token connections keep working, and you can switch between the two methods.
- New NinjaOne tools:
- Update which devices an end user can access. You can add and remove up to 100 devices in one call. Available on Pro.
- Set a user role's organization permissions.
- A raw read tool (Free) and a raw request tool (Pro) for NinjaOne API endpoints that don't have a dedicated tool yet.
- Authorize all customers (Microsoft Graph and Azure). If you connect Microsoft with your own app registration, a new panel on the Microsoft Graph and Azure cards grants your app's permissions in every GDAP customer tenant through Partner Center.
- Preview first. You can preview the customer list and permissions before anything changes.
- What a run grants. Each run applies the Microsoft Graph and Azure permissions defined in your app registration.
- Run behavior. If a customer refuses, Microsoft's reason is shown and the run continues. The run stops if sign-in fails or Microsoft throttles requests.
- Large customer lists. Each run covers up to 1,000 customers, and "Continue with the next customers" picks up the rest. Progress is tracked by customer, so customers added or removed between runs are not skipped.
- Where the panel appears. The panel shows when your own-app credentials are on the shared connection or on your personal connection.
- Run from PowerShell. The same process can be run from your own PowerShell session, including a dry-run option. The Microsoft Graph help page explains how.
- Partner Center permission in app setup. The own-app provisioning script now adds the Partner Center permission that Authorize all customers needs. If you already created your app, the help page explains how to add it: re-run the updated script against your existing app, or add the permission in the Entra admin center and grant admin consent once.
Improvements
- Microsoft consent takes effect right away. When a customer administrator grants consent, StackJack now discards that customer's cached Microsoft tokens. Previously, new permissions could take up to an hour to apply. This covers consent through the per-customer consent link and through Authorize all customers.
- Clearer Halo "Ticket not found" guidance. Halo returns the same "Ticket not found" message for two different problems when adding an action:
- the ticket ID doesn't exist, or
- the related record, such as an opportunity or project, is outside what your Halo agent and API application can access.
StackJack now explains both causes and what to check: the ID, the API application's permissions (opportunities fall under CRM and Sales), the agent's role, and re-authorizing.
- NinjaOne end-user tools accept more options.
- Creating an end user can send an invitation.
- Listing an organization's end users can include their roles.
- Listing roles can be filtered by role type.
- The end-user details tool now notes that its response lists the devices that user can access.
Bug fixes
- Ingram Micro connection checks. A healthy Ingram Micro connection could fail its check and be automatically disabled if the app wasn't subscribed to Order Management. The check now passes when any of the order, catalog, or price-and-availability services answers. A connection is treated as having bad credentials only if every service refuses it.
- AI Governance scan coverage. Some records from ingest sources, such as OpenTelemetry and Copilot Interactions, were marked as incompletely scanned when a detection rule set hadn't finished loading. This could raise a scan-coverage alert almost every hour. Those records are now scanned fully.
Fixed customer-reported issues
- Request for NinjaOne tools to manage which devices an end user can access, plus a general way to call NinjaOne API endpoints without a dedicated tool (
01M5B2J75QPT6DVK91KB3HVE9R). Added a NinjaOne tool to update end-user device access and a raw read/request tool pair. - Request to connect Cloudflare by signing in instead of using an API token (
01M5BTMPYNN69RM73VKXJQ40WZ). Added Sign in with Cloudflare alongside API-token connections.