Inmanta Service Orchestrator 9.3 is about trust and comfort: the orchestrator now actively protects itself against operational accidents, logins and API tokens are ready for production use without an external identity provider, and the web console removes a lot of day-to-day friction.
The orchestrator protects itself
Mistakes happen: a forgotten server instance left running during a migration, a restored VM snapshot, a database failover. In 9.3 the orchestrator handles these situations by itself.
- Only one server can be active on a database. A second server pointed at the same database simply refuses to start, and a server that loses its claim (for example after a database failover) shuts down instead of corrupting state.
- After a failover or a wiped disk, a server detects that its local files are out of date and automatically triggers a recompile to catch up.
No silent corruption, no manual cleanup. This also makes an active/passive high availability setup easier to operate: point a standby server at the same database and it takes over as soon as the active one goes away.
Logins ready for production
The built-in database login (username and password, no external identity provider needed) is now production grade:
- Passwords must be strong (minimum 12 characters, mixed character classes), and changing your own password requires the current one.
- Sessions expire after an hour, but the console renews them silently while you work, so you are never logged out mid-task.
- Every login attempt, successful or not, is logged with the username and source IP.
And if you use OIDC single sign-on: when your identity provider is down, an admin can now still get in through a break-glass database login and keep managing the platform. For advanced password policies, MFA or SSO, an external OIDC identity provider remains the way to go.
API tokens you can actually manage
Tokens used to be write-only: once issued, you could not see them, and revoking one meant rotating the signing key and breaking everything else. In 9.3, tokens are registered by default: the new Tokens tab in Settings shows every token with who created it, what it can do, when it was issued and last used. Give tokens an expiry when you create them, and revoke a single leaked or retired token with one click, without touching the others.
Find what you need on the Resources page
The Resources page now has sorting (including by state), an orphaned filter, and boolean filters with clear include/exclude toggles. A Reset Filters button brings you back to the default view in one click, and status popovers use human-readable labels instead of raw status keys.
Friendlier service forms
Filling in a service instance is much more pleasant:
- Dictionary fields get a real JSON editor with syntax highlighting instead of a plain text box.
- Optional yes/no fields are a clear True/False toggle instead of radio buttons.
- Long forms can be organized into named tabs, defined by the service model.
- Suggested values can show human-friendly labels while submitting the technical value underneath.
See what changed between versions
The attribute compare view now lets you search for a version, shows when each version was created, and puts the differences side by side. Facts, parameters and attribute values are rendered based on what they contain: JSON and XML open in a formatted read-only editor with copy and download buttons, so no more squinting at one-line blobs.
Also in this release
- Orders view: clearer progress states and direct links to the service instances they created.
- The instance composer loads faster and no longer freezes when the catalog refreshes.
- A batch of scheduler and executor fixes that remove leaked processes and avoidable deployment latency.
For the full list of changes, see the detailed technical release notes or the changelog.