Sign in with Stello
Coming soon · PlannedGive people a familiar way to sign in to your own app with their Stello account. For example, a student association could offer Sign in with Stello in its member portal instead of asking everyone to create another password.
The intended experience
- A person chooses Sign in with Stello inside your app.
- They continue to Stello to sign in and review what your app is requesting.
- After approval, they return to your app, which establishes its own session.
The sign-in experience is planned around OAuth authorization and OpenID Connect identity. The protocol details, supported application types, identity claims, consent screen and registration process are still being designed.
Identity and organization access are separate
Signing in identifies a person. It does not grant access to an organization’s events, member lists, payments or dashboard. Your application will need to request supported permissions, obtain consent where required, and enforce its own access rules.
Organization API keys remain server credentials for organization-owned integrations. They are not user login tokens and cannot be placed in a Sign in with Stello button.
Planned developer setup
We expect an application registration flow with approved redirect URLs, clearly named applications, requested scopes and revocable access. Public and confidential clients need different credential handling; the final registration contract will document those differences.
There are no authorization URLs, token endpoints, discovery documents, client IDs or sign-in SDKs available for this integration yet. Do not build against Stello’s internal dashboard authentication routes. This preview is not a production authentication specification.