Login buttons you can add.
Each provider shows how the login is verified and whose OAuth credentials it uses: ours, so you set up nothing, or your own, so the consent screen shows your name. Adding a provider is one module; ask for one you miss.
Login buttons you can add.
Amazon
Sign in with an Amazon account (Login with Amazon). Amazon returns no ID token, so MyLogin.world exchanges the code and reads the profile from the Amazon API — the result is attested by MyLogin.world, not signed by Amazon. Works with MyLogin.world credentials or your own security profile.
- Credentials
- Ours, or your own
Apple
Sign in with Apple. Apple signs a nonce-bound ID token, so the sign-in cannot be replayed. Apple requires a paid developer account and issues credentials per team, so these are always your own. Users may hide their real address behind an Apple private relay.
- Credentials
- Your own
Discord
Sign in with a Discord account. Discord returns no ID token, so MyLogin.world exchanges the code and reads the profile from the Discord API — the result is attested by MyLogin.world, not signed by Discord. Works with MyLogin.world credentials or your own Discord application.
- Credentials
- Ours, or your own
GitHub
Sign in with a GitHub account. GitHub returns no ID token, so MyLogin.world exchanges the code itself and reads the verified primary email from the GitHub API — the result is attested by MyLogin.world, not signed by GitHub. Works with MyLogin.world credentials or your own OAuth app.
- Credentials
- Ours, or your own
GitLab
Sign in with GitLab — gitlab.com or your own self-hosted instance. GitLab signs a nonce-bound ID token, so the sign-in cannot be replayed. Works out of the box with MyLogin.world credentials on gitlab.com, or bring your own application.
- Credentials
- Ours, or your own
Sign in with a Google account. Google signs an ID token bound to a nonce MyLogin.world generates, so the sign-in cannot be replayed. Works out of the box with MyLogin.world credentials, or bring your own Google Cloud OAuth client.
- Credentials
- Ours, or your own
Microsoft
Sign in with a Microsoft work, school or personal account. Microsoft signs a nonce-bound ID token. Microsoft requires your own app registration, so these credentials are always yours.
- Credentials
- Your own
OpenID Connect (custom)
Connect any standards-compliant OpenID Connect identity provider — Authentik, Keycloak, Authelia, Okta, Auth0, Zitadel and others. MyLogin.world discovers the endpoints from the issuer and verifies the ID token signature against its published keys.
- Credentials
- Your own
ORCID
Sign in with an ORCID iD — the persistent identifier used by researchers. ORCID signs a nonce-bound ID token whose subject is the ORCID iD itself. ORCID issues credentials per organisation, so these are always your own. Most ORCID records keep the email address private, so accounts usually arrive without one.
- Credentials
- Your own
Slack
Sign in with Slack. Slack signs a nonce-bound ID token containing the member’s verified work email, so the sign-in cannot be replayed. Works out of the box with MyLogin.world credentials, or bring your own Slack app.
- Credentials
- Ours, or your own
Twitch
Sign in with a Twitch account. Twitch signs a nonce-bound ID token, so the sign-in cannot be replayed. Works out of the box with MyLogin.world credentials, or bring your own Twitch application.
- Credentials
- Ours, or your own
Passkeys
Face ID, Touch ID, Windows Hello, security keys. Register once, use on every service.
Authenticator app (TOTP)
Second factor with any standards-compatible app. Recovery codes included.
Provider names and logos belong to their owners and do not imply endorsement. Where a provider limits eligibility, the card says so.
Give your app a real sign-in today.
Free for personal use. Supporter is $5 a year when you outgrow it.