On this page
In short#
MSO Cloud is the sign-in, membership and entitlement core for a family of separately deployed apps. A customer keeps one credential, one launcher and one admin screen, and each app keeps its own code, database and release cadence.
The binding decision is ADR 0058. The full arc42 write-up with C4 diagrams is App family and identity hub; the API and event contract is Platform API and events.
How it works#
- One sign-in. MSO Cloud is the only OpenID Connect issuer. Apps are relying parties: they accept its tokens and keep no passwords for linked users. Password, passkey, two-factor, directory and organization OpenID sign-in all end in one MSO session.
- Launcher. Every app renders the same grid of enabled apps from one endpoint. Opening an app carries the organization and brand with it, with no second sign-in. A member on an organization host or custom domain crosses through a single-use handoff token bound to the session id; the issuer runs only on the platform host.
- Entitlement per organization. "Organization X has app Y on plan Z until date D" is one row in the plugin install ledger, which carries plan, limits, validity and status. A trial is a validity date. The launcher shows an app as enabled, not enabled or expired from that row, and the Platform API serves it at the entitlements endpoint.
- Roles. The MSO role sets a floor in each app: owner, admin, editor and viewer map to owner, admin, creator and viewer. An app may add finer roles above that floor.
- Provisioning. Users and memberships are created at first login from token claims. Later changes arrive as signed, idempotent webhooks:
org.app.changed,membership.changed,user.disabled,trends.updated. - Logout everywhere. Signing out in any app revokes the server-side session (
sid) and sends a back-channel logout to every app that holds it.
Data ownership#
Each dataset has one owner. Others read it through a scoped API and never hold a database connection to it.
| Data | Owner | Others get it by |
|---|---|---|
| Marketplace, marketing and third-party market-intelligence data | MSO Cloud | Platform API, one scope per data plane, plus webhooks |
| The shared social trend feed | MSO Cloud | Synced once in MSO Cloud; an app pulls it into a local projection |
| Dashboards, charts and AI analysis | MSO Cloud | A deep link from the launcher, never an embedded frame |
| Briefs, generated assets, render jobs, approvals and schedules | The app | Not shared; publish events carry identifiers only |
| Performance of a published creative | MSO Cloud | Its own connectors pull it and attribute it by the lineage |
An app may keep a read-through copy of data MSO Cloud owns, so a render never waits on MSO uptime. The trend feed is synced once in MSO Cloud, not by each app: an app pulls it when the revision changes, keeps its own copy, and reads that copy only for orgs whose grant MSO confirmed in the last 3 hours (a denied grant is removed at once). The three data planes still never mix; the feed is a separate shared dataset (Data planes and the warehouse).
Standards followed#
| Control | Standard |
|---|---|
| Authorization code flow with PKCE for every client | OpenID Connect Core 1.0, RFC 7636, RFC 9700 |
| Apps authenticate with a signed assertion, not a secret | RFC 7523 (private key JWT client authentication) |
| JWT access tokens with a fixed audience and one org | RFC 9068, RFC 8707 resource indicators |
| Exact redirect URIs; dynamic registration off | RFC 9700 (OAuth 2.0 Security Best Current Practice) |
| Refresh-token rotation with family revocation | RFC 9700 |
| Revocable server-side session id | OWASP ASVS, session management |
| Logout to every app | OpenID Connect Back-Channel Logout 1.0 |
| Account linking only with proof of both accounts | OWASP ASVS, authentication |
| Signed webhooks with replay protection | HMAC-SHA256 with an event id |
Where it stops#
- Step-up authentication before a sensitive app action, seat caps and home-realm discovery are directions, not behaviour: Future direction.
- Per-capability readiness, including which organizations use which app, is on Project status.
- Apps get tokens, platform API reads and signed webhooks. They never get a connection to the MSO database, cache or assistant tools.
- Analytics stay in MSO Cloud. An app shows only small pickers built from API data and links out for the rest.
- Choosing a different sign-in library for the web app is a separate decision.