Single sign-on (SSO)

How single sign-on connects an app and its community, and what to get right on tokens and sessions.

November 17, 2026

Single sign-on (SSO) is an authentication arrangement that lets a person use one sign-in process to access several connected applications or services. In an embedded community, the host app authenticates the member and passes trusted identity information to the community service, with no separate password. SSO is an identity and session design: connected services do not automatically share the same permissions. You still need to validate assertions, manage sessions and decide what happens when users sign out or lose access.

At a glance

Glance intro

What it does
Reuses an established authentication relationship across connected services.
Typical role
An identity provider authenticates a person; a relying party accepts the assertion.
In-app example
The app signs in a member who then opens its embedded community.
Main limit
Authentication does not automatically determine permissions or session termination.

How single sign-on works

SSO separates the party that authenticates a person from the services that rely on the result. The OpenID Foundation's OpenID Connect specification describes an identity layer built on OAuth 2.0, in which a client verifies the end user's identity based on authentication by an authorization server, communicated through an ID token.

NIST's 2025 digital identity guidance describes federation as a way for a credential service provider to share authentication attributes with separately administered relying parties. The relying party never accepts an identity claim blindly: it needs a defined trust relationship and a way to validate the assertion before opening its own session.

In an app-plus-community integration, one system keeps responsibility for the original sign-in while the embedded community receives only what it needs to recognize the member. Behind the visible “one login” sit technical responsibilities: account mapping, token verification, expiration and permission checks.

Integrating SSO into an embedded community

Decide which service is the identity provider and which relies on it. Define a stable member identifier, when a signed assertion is issued and where the receiving service validates it. If you use JSON Web Tokens, RFC 7519 defines their claims format, including issuer, subject, audience and expiration.

Review session expiry, sign-out, account deletion, lost credentials and changes in membership status. A person can be authenticated in the app and still lack access to a given group, so you need a separate authorization model that decides who may read or publish each category of content.

SSO also affects privacy. Apple's app privacy documentation requires disclosure of data collected by an app and its partners, and the European Data Protection Board assigns different duties to controllers and processors. Send the embedded provider only the personal information it needs, and document who can access what (see first-party community data).

Security and operational limits of SSO

With SSO, correct assertion validation becomes central to access control. OpenID Connect defines ID token validation requirements: check issuer, audience, signature, validity period and the relevant claims for your profile. NIST stresses appropriate authentication assurance and federation controls rather than one configuration for every scenario.

Plan recovery paths for when the identity provider is unavailable. An interface that looks logged in must not keep community access open for an expired token or a revoked account: reconcile local sessions with the authoritative identity state, and log authentication failures without exposing tokens.

SSO connects authentication for known relying services. It does not transfer ownership of user data or grant access to external platforms. Document what the product controls, what the provider controls and how the connection can be cut.

Single sign-on vs. separate community login

With SSO, members reuse the app's identity flow; their identity must be recognized across systems, and the security work is correct federation and assertion validation. With a separate community login, members sign in again, a member record is created separately, and you take on separate credential and session management. In both cases, you still need access rules for groups and actions.

At Octopus

Your app stays the identity provider for its community. Your backend signs a JSON Web Token for each member, and we receive a user ID: members never create another account or password. Separate sandbox and production communities let your developers implement and test the flow safely.

Members go from your app to its community in one tap, already signed in. See the integration on the developers page and in our Community SDK guide.

Book a demo →

Frequently asked questions

What is single sign-on (SSO)?

A way for one authentication process to give access to several connected services. A person signs in with an identity provider, and other services rely on a verified assertion instead of collecting a separate password. OpenID Connect defines an identity layer on OAuth 2.0 for this. SSO does not give every application unrestricted access to the account: you still need authorization rules, trusted token validation and clear behavior when a session expires or an account is disabled.

How does SSO work in a mobile app?

The app's authentication system is linked to a connected service. The user signs in through the usual account flow, and the connected service receives identity evidence it can validate. NIST describes federation as authentication information shared with relying parties through assertions. In an embedded community, define who issues the assertion, who validates it, which identifier maps accounts and how sessions end. One valid login does not grant permission to every group or action.

Is SSO the same as OAuth?

No. SSO describes a user experience and an authentication arrangement; OAuth 2.0 is mainly an authorization framework. OpenID Connect adds an identity layer on top of OAuth 2.0 so clients can verify authentication and obtain claims about a user. An access token for a resource is not proof of identity. Use the right protocol profile, validate identity tokens as specified, and define permissions independently of authentication.

Does SSO require a JSON Web Token?

Not always: the assertion format depends on the federation design. OpenID Connect uses an ID token represented as a JWT. RFC 7519 defines how claims such as subject, audience and expiration are represented, but not every JWT is suitable for authentication. Follow your protocol's specification, validate signatures and claims, and never treat a token's readable payload as proof that it came from a trusted issuer.

What happens when a user signs out of an SSO-connected app?

Connected sessions do not necessarily end at the same moment. Sign-out depends on the provider, the protocol profile and your session design: the host app can end its local session while a connected service keeps its own session until it receives a logout signal or the token expires. Test sign-out, token revocation, account deletion and membership removal, and document which component can invalidate access and how the interface handles an expired session.

Is SSO secure for an embedded community?

It can be, depending on implementation and operational controls. OpenID Connect and NIST digital identity guidance stress trusted assertions, correct validation and appropriate authentication assurance. The app also decides which members can view or publish content. Review provider documentation, limit token exposure, test failure states and keep personal information passed to supporting services to a minimum. An SSO setting alone does not make a system secure.

Sources
  1. OpenID Foundation. OpenID Connect Core 1.0 incorporating errata set 2. Published December 15, 2023. Accessed November 11, 2026.
  2. National Institute of Standards and Technology. Digital Identity Guidelines: Federation and Assertions. Published July 2025. Accessed November 11, 2026.
  3. National Institute of Standards and Technology. Digital Identity Guidelines: Authentication and Authenticator Management. Published July 2025. Accessed November 11, 2026.
  4. Internet Engineering Task Force. JSON Web Token (JWT), RFC 7519. Published May 2015. Accessed November 11, 2026.
  5. Apple Developer. App privacy details on the App Store. Accessed November 11, 2026.
  6. European Data Protection Board. Data controller or data processor. Accessed November 11, 2026.

Turn your users into a retention engine.

Book 30 minutes with us. We’ll show you the SDK running inside an app like yours.