SeleContinue with SeleID: how sign-in for your own app will work
How Continue with SeleID works for outside developers: OpenID Connect with PKCE, consent screens, and what is open today.
Published by SeleTech
Short answer
Continue with SeleID lets people sign in to your app with the same account they use in SeleVista and SeleVerse. It is built on OpenID Connect with an authorization code and PKCE, the standard pattern behind other large sign-in buttons, so existing OpenID libraries can talk to it.
The flow has three steps. You register an app in the developer console and set its redirect addresses. You send people to the SeleID authorize endpoint, where they sign in and see a consent screen that names your app and the permissions it asks for. They come back to your redirect address with a code, and your app exchanges that code for tokens. Mobile and single-page apps register as public clients and rely on PKCE instead of a secret.
Today, sign-in is live for SeleVista and SeleVerse. Sign-in for outside apps is built but switched off: Outside apps are coming soon.
Frequently asked questions
Can I add Continue with SeleID to my app today?
Sign-in is live for the Sele apps. Outside apps are coming soon.
Which standard does SeleID use?
OpenID Connect with the authorization code flow and PKCE. Discovery is published at auth.seleid.dev/.well-known/openid-configuration.
What does a person see when they sign in?
A consent screen that names your app and the permissions it asks for. They can decline, and your app then receives an access_denied error.
Is there an SDK?
A TypeScript client is coming soon. Kotlin and Swift SDKs are planned; native apps can use a standard OpenID library meanwhile.