StackJack 0.1.0.6345+a1b9aa2

This release updates the Moovila connector for Moovila's self-service API access: you now connect with a Client ID and Client Secret instead of a token, and first-time setup works again. It also makes the Connectors page load faster for tenants with several connectors.

New features

• Moovila connector: self-service authentication. Moovila no longer issues API tokens, so the connector now signs in with the Client ID and Client Secret you get when creating an API client in Moovila. You no longer need to contact a Moovila representative to set up the connector. Connections configured before this release keep working exactly as before; nothing needs to be re-entered.

Improvements

• The Moovila configuration form now asks only for a Client ID and Client Secret. The Token field has been removed. When editing a connected Moovila connection, leaving the Client Secret blank keeps the one already stored.
• The Moovila setup guide is now three steps (create the API client, paste the pair, test), and the connector documentation and troubleshooting entries have been rewritten to match the new sign-in method.
• Moovila error messages now tell you what to do yourself: an authentication failure points at checking the Client ID and Client Secret, and a permissions failure explains that the API client lacks read access, rather than referring you to Moovila.

Optimizations

• The Connectors page loads noticeably faster for tenants with several connectors and connections. Credential lookups for the connector cards are now resolved together instead of one at a time. What the cards show is unchanged.

Bug fixes

• Saving a first-time Moovila configuration failed with a message asking you to re-run an authorization flow that Moovila no longer offers. Removing and re-adding the connection did not help. First-time configuration, adding a second Moovila connection to an already configured tenant, and later edits of such connections all save correctly now.
• Using "Add connection" on the Moovila connector did not require a Client Secret and showed a "leave blank to keep the current one" hint that did not apply. It was possible to save a new connection that could never authenticate. The secret is now required when adding a connection, and the hint appears only when editing an existing one.
• The corrected Moovila "invalid credentials" guidance was not actually shown for the most common failure case; it now appears when Moovila rejects the Client ID / Client Secret pair.
• An existing Moovila connection whose token was rotated by Moovila could lose the replacement token and stop working. The rotated token is now retained.
• Moovila access tokens could in some cases be treated as already expired, causing a fresh login on every request. Token lifetimes are now interpreted correctly so sessions are reused as intended.