Skip to content
MSO CloudDocumentation

Future direction

On this page

In short#

These are the directions the architecture is set to take, each with the document that sources it. Nothing here is a commitment to a date; whether a direction has started is on Project status.

Where the architecture is heading, by trackIdentityConformance suite + external issuerreviewsource: plan phase 3Step-up authentication (acr_values,max_age)source: plan phase 5, ADR D14Home-realm discovery: email to orghostsource: ADR D13, plan phase 5Data and eventsDaily count reconciliation, 14-daywindowsource: plan phase 3-4, ADR D15Seat assignments per app(org_app_assignments)source: ADR D7, plan phase 5SCIM-style provisioning, only for athird-party appsource: ADR D8, rejected for v1Platform and stackSecond app on the kit in <= 2engineer-weekssource: plan phase 6Suite navigation package, on atriggersource: ADR D12Sign-in library move: separatedecisionsource: ADR 0059, gate 2027-Q2
Directions only, each with the document that sources it. Dates and state are on the status page.

Sources: ADR 0058 (app family and identity hub), the app family hub plan (phases table), and the architecture hub industry research.

Directions from the decision record#

Direction Why Source
OpenID conformance suite after every issuer library minor, and an external review of the issuer before the second customer org An identity provider is a standing operating cost; a repeatable suite keeps upgrades safe ADR 0058, Consequences; hub plan phase 3
Step-up authentication: acr_values and max_age, with an MSO re-verify screen A sensitive app action needs a fresh second factor without a second login system Hub plan phase 5; ADR 0058 D14
Home-realm discovery: email to organization host, then the handoff A white-label member should reach the branded sign-in without knowing the platform host ADR 0058 D13; hub plan phase 5
An app host on the customer's own domain Removes msocloud.net from the address bar during sign-in ADR 0058 D13; hub plan phase 5
Seat assignments per app (org_app_assignments), with a seat refusal in the app A seat-capped plan needs to know who may use an app, without carrying a role ADR 0058 D7; hub plan phase 5
More Platform API scopes (marketing, marketplace), each added when a consumer exists One scope per data plane keeps the planes apart ADR 0058 D10; platform-scope-per-plane audit
A second app on the satellite kit in 2 engineer-weeks or less Proves the contract and conformance specs are reusable Hub plan phase 6
A React suite-navigation package, only when a second React app arrives or the screenshot-parity gate fails twice A shared component earns its cost only after the markup contract strains ADR 0058 D12
Moving the web app's sign-in library, decided separately The issuer contract is frozen, so apps do not notice the move ADR 0058 D14 (gate 2027-Q2); hub plan phase 6

Industry practice the design tracks#

Practice How it applies Source
OAuth 2.1 behaviour: code flow with S256 PKCE, exact redirect matching, no implicit grant Already the issuer's behaviour; the specification is still a draft, so the design tracks behaviour rather than a version Industry research section 2.1; ADR 0058 D2
OpenID Back-Channel Logout, not front-channel Front-channel logout breaks when apps sit on different registrable domains and browsers partition cookies Industry research section 2.1
Sender-constrained tokens (DPoP, RFC 9449) Implemented by the candidate library compared in the sign-in library decision (ADR 0058 D14); the current issuer does not use it Industry research section 2.1
Token exchange (RFC 8693) so a worker acts as a user for one org Rejected for the first version because no consumer needs it ADR 0058, Rejected; industry research section 2.1
SCIM 2.0 provisioning (RFC 7643, RFC 7644) Reserved for a third-party app; first-party apps provision from claims and webhooks ADR 0058, Rejected and D8; industry research section 2.1
Entitlement as commercial right, then assignment, then permission Matches the ledger row, the future seat table and the app's own roles; usage-based limits wait for metered pricing Industry research section 6
Versioned, per-tenant read models with contract tests in both repos' CI The contract package and the count reconciliation are the first two parts Industry research section 5; ADR 0058 D15
Platform core with separately deployed apps, never a shared database Shared tables across deployables recreate coupling without enforcement Industry research sections 1 and 5; ADR 0058 D1

What the design avoids#

Merging the repos, an iframe shell, path zones on the platform host, a hosted identity vendor, front-channel logout and per-host issuers are rejected with reasons in ADR 0058, Rejected.

Where it stops#

  • Directions and their sources are listed here. What has started is on Project status.
  • The industry research is a comparison of practice, not a commitment, and the design takes only what ADR 0058 adopts.