StackJack 0.1.0.14967+582c492
StackJack 0.1.0.14967+582c492
This release adds support for NinjaOne branded sign-in addresses. Secret values such as passwords, keys and tokens are now left out of tool answers on hundreds of tools unless you ask for them. It also changes how the Activity log records calls made with shared keys, fixes a website checkout issue, and makes several display and help-center improvements.
New features
- NinjaOne branded addresses. If you use NinjaOne Branding and your API client only signs in on your branded host, you can now connect it. On the Connectors page, the NinjaOne region list has a new Branded address option. Enter your hostname and choose the regional ending (rmmservice.com, .eu, .ca or .com.au), and StackJack builds the address for you. When you edit an existing branded connection, the form opens with your hostname and ending already filled in. The setup guide and the NinjaOne help page cover the new option. If NinjaOne reports that the client app does not exist, the error message now points you to the branded address choice.
Improvements
- Clearer Activity log attribution for shared keys. Calls made with an organization-level API key or Client ID and Secret from the Endpoints page no longer show the organization owner as the person. The log now shows the key's own name and no person. Automations with no run-as person also show their own name. Sign-ins and personal keys still record the person who made the call. Rows recorded before this release are unchanged.
- Help center corrections.
- The AI Governance page now explains what happens when your sign-in is too old to use governance tools. Your AI tool shows a refusal and does not start a new sign-in. To fix it, disconnect StackJack in your AI tool, connect again, and sign in with single sign-on or a second factor. A refreshed connection keeps its original sign-in time.
- The data residency page now lists the correct US data locations.
- The external data processing page now includes Twilio (used for AI Governance text alerts) and Microsoft Azure AI Foundry.
- The external data processing page now correctly states that the automation builder's wizard and AI-assist suggestions run on your own AI key when you have provided one. If that key cannot serve the request, the request is refused rather than moved to StackJack's key.
Bug fixes
- No duplicate charges for connectors you already have. When you buy a connector on the website and your organization already holds it at a paid tier, you are now sent to the Portal to manage it instead of being offered a second checkout. This applies to all of these cases:
- Plans granted to your organization, including Enterprise plans.
- Trials you bought out during the trial.
- Purchases above a trial's tier.
UI & UX changes
- The Roles editor dialog now uses more of the screen on large displays, so tool names in the tool picker are less cramped. Small screens are unchanged.
- The public connector directory now uses current vendor names: ConnectWise PSA (Manage) and NinjaOne (NinjaRMM). Searching for the old names still finds them.
- Several connectors moved to categories that better match what they do:
- AbleSign and WordPress moved to Marketing.
- Rewst moved to Reporting & Analytics.
- Employment Hero moved to Finance & Accounting.
- Fireflies moved to Project Management.
- A new AI Administration category holds the Anthropic Admin, OpenAI Admin, GitHub Copilot and AI Governance connectors.
- The connector directory now counts only the tools you can actually connect to. Rewst's listing now shows its available tools only.
- Vanta, Huntress and Propel Your MSP now show the vendor's own logo for dark backgrounds, so they are readable on dark tiles.
Breaking changes
- Secret values are left out of tool answers by default. Hundreds of tools across about 40 connectors now remove passwords, keys, tokens and similar secret fields from their answers unless you ask for them. Affected connectors include 3CX, Cloudflare, ConnectWise, Cove, Dropsuite, Island, Jamf, MySonicWall, PagerDuty, Slide, Twilio, Veeam, WatchGuard and Xero.
- Each affected tool has an
includeSecretsargument. A few tools use a differently named include argument, which is shown in their input schema. - The tool's description names the fields it removes.
- If you need a secret value, set the include argument to
true. - Before you read a record and send the whole record back in an update, read it with the include argument set to
truefirst. Otherwise you could clear the stored secret. The affected update tools say this in their descriptions.
Fixed customer-reported issues
- NinjaOne connections could not be set up for accounts that only sign in on a custom branded address.
01M73SG8N5CWEK071H134T4HAX. You can now choose Branded address when connecting NinjaOne. - AI Governance tools returned a second-factor refusal for a user enrolled in multi-factor authentication, and the help page did not explain how to resolve it.
01M7BT3KFFHJPKKD4VMXWZCKBD