Moving from another sign-in provider

Add Sign in with Atheron beside the provider you use today, link existing accounts safely, and switch over.

Melden Sie sich an, um Ihre eigene Test-Client-ID in den Beispielen zu sehen.

Sign in with Atheron is standard OpenID Connect, so the library you use for another provider (Google, Auth0, Okta and the like) already speaks it. Moving is mostly configuration and one careful step: linking the accounts you already have.

1. Add Atheron beside what you have

Register your app, point your OIDC library at our discovery document, and add a Sign in with Atheron button next to your current one. Keep both until you are ready.

2. Link accounts safely

The first time somebody signs in with Atheron, you will not have their sub yet. Link it to an existing account only when one of these holds:

• They are already signed in to your app with the old provider when they connect Atheron. This is the safest way.
• The email we send has email_verified true and it matches an account whose email you verified yourself.

Never link on an unverified email. Once linked, store sub on the account and key on it from then on.

3. Switch over

When most people have linked, make Atheron the main button. Keep the old provider for anyone who has not linked yet, and tell them how.

Upgrading an SDK

Our SDKs follow semantic versioning: a patch fixes, a minor adds, a major can break. Every change is in the changelog.