Skip to main content

13.7 What Changed in OLIVE 1.3

OLIVE 1.3 is primarily a security release. Most of it is invisible while you work normally, but a number of things that used to be permitted no longer are.

This page is the checklist: every change that can affect connectivity you have already built, with a pointer to where it is explained. If you are moving content from a 1.2 deployment, read it once before you import.

Reading order

If you only read one thing, read Security in Connectivity Engineering. This page is a summary of what changed; that chapter is the reasoning behind it.


Things that can break existing connectivity​

ChangeWhat it means for youWhere
Calls to internal addresses are blockedA datapoint that reached an in-cluster service, an internal host or a link-local metadata address is refused and logged as OLIFETCH1. This includes a service of your own hosted in the cluster. Public destinations are unaffectedSecurity in Connectivity Engineering
Placeholders are validated per HTTP positionWhich characters a placeholder may produce now depends on where it appears — host, port, method, query key or value, header value, body. Header names can no longer be substituted at allPlaceholder Resolutions
Session IDs are issued by the platformThe ID is generated when you store the first item and returned to you; every later read and write must use that ID. A session ID supplied by the caller is rejectedService APIs
Jobs belong to the user who started themPolling, setResponse, pause, cancel and resume verify the caller. A job ID alone is no longer enough; continuing someone else's job needs the explicit optionSecurity in Connectivity Engineering
A file key or URL no longer grants accessRead and write paths are separated, system files cannot be overwritten, and names, extensions and MIME types are validatedFile Handling in Connectivity
Upload keys are validatedA key may contain letters, digits and - _ . ~ @ / only. A space — in a file name or anywhere in a flattened path — is rejected with key contains unsupported charactersFile Handling in Connectivity
Uploaded files have a categorycore, static or temp, and the category decides who may overwrite the file. An upload that passes none is a temp file, writable by every user of the tenant. Writing static needs the editor role, core the admin roleFile Handling in Connectivity
Pilets may call only three thingsThe local paths /data-orchestrator/ and /repository/get, and the public file-storage-service API with GET. Everything else, uploads included, goes through the orchestratorClient Microfrontends

Things that need a different role​

All three were available to an editor in 1.2 and require admin in 1.3. A development deployment has no roles, so none of this is visible there — it appears when the work moves to production.

OperationWhere
Importing an OLIVE Connectivity BundleHow to Package a Use Case Solution
Editing connectivity entries tagged coreUser Interfaces
Deploying or changing a piletClient Microfrontends

The roles themselves are also genuinely enforced now, where before they mapped to the same permissions. Connectivity still runs with the permissions of whoever executes it — which is why administrators should not execute connectivity.

Things that changed shape​

ChangeWhat it means for youWhere
No common assets sandboxThere is no shared library sandbox any more. Reusable content moves between ordinary sandboxes as a bundle; an import goes into one sandbox onlyHow to Package a Use Case Solution
Export and import are named OCBThe editor calls them Export as OLIVE Connectivity Bundle (OCB) and Import OLIVE Connectivity Bundle (OCB). Same mechanism, clearer name — and its main job is delivering a solution from development to production, not only backupHow to Package a Use Case Solution
The Temporal Web UI is off by defaultAsk your OLIVE operator or administrator to enable it on a development deployment when you need itTroubleshooting & Debugging
Security events have stable codesDenials are visible in the log rather than appearing as silent partial failures — OLIFETCH1 for a blocked destination, OLIAUTHZ2 for a missing role, and so onSecurity in Connectivity Engineering

Before you import 1.2 content into 1.3​

  1. List the destinations your http datapoints call, and check none of them is an internal address.
  2. Check any placeholder that produces a http header name, or characters outside the usual set.
  3. Check any component or script that uses the session memory and verify it confirms with the new API format: On setting values no session ID is provided and on getting values the session ID returned from settting is used.
  4. Check any pilet that calls a service other than the orchestrator, or uploads to the file storage directly.
  5. Check every upload: anything that is not throwaway runtime data needs an explicit category, and temp files are best uploaded without a static key.
  6. Make sure the person doing the import holds the admin role.

If a case genuinely cannot be reworked — your own service hosted in the cluster, or an internal system with no external endpoint — raise it with your tenant administrator rather than working around it. The security chapter describes how.