OpenMax
Free Trial

Out of scope

Capabilities the platform does not provide today: SSO, app identity tokens, frontend-only apps, a general postMessage bridge, hosted backends, and host-side capabilities not planned for now.

Out of scope

This page lists capabilities the platform does not provide today, and which ones already have alternatives. Do not design your app to depend on anything listed here.

  • SSO: the platform does not do unified single sign-on / single sign-out: it does not sync sign-in state, does not notify sign-out, does not create accounts for apps, and does not connect to an app's own IdP. Apps that use authorization (see Sign-in) to map OpenMax identities to local accounts are doing their own implementation, covered in "Integrating existing systems", and are not affected by this item.

  • App identity tokens (and organization-level tokens): Not planned for now. Background jobs run as the user with offline_access.

  • Frontend-only apps (PKCE public clients): Deferred.

  • General postMessage bridge: Deferred. Right now the host and the app exchange only these fixed messages:

    • Theme / language (see Open modes and URLs);
    • App → host route sync (openmax:location, path only);
    • Sign-in when embedded (requestAuthCode: the host only hands over a code; your backend still exchanges the token);
    • App requests to open a conversation (openmax:navigate:request, see Open modes and URLs).

    Host capability calls are still deferred. Sign-in when embedded does not provide an SDK helper for server-side token exchange; how the app stores its session is up to the app.

  • Host-driven app navigation, iframe size negotiation, query / hash sync: Not planned for now. "Host-driven app navigation" here means the host making pages inside the app navigate; the app asking the host to open a conversation is not part of this.

  • Hosted app backends: you deploy the backend yourself.

Route sync, sign-in when embedded: Live. App requests to open a conversation: Coming soon.