Olaryn IdentityShared sign-in for Olaryn products

Passkeys, email links, Google and GitHub on your own sign-in screen. The identity service handles authentication for our products.

Shared identity service. Used across Olaryn products.

  • Built in
  • Passkeys
  • Email links
  • Google
  • GitHub

Supported sign-in methodspasskeys, email and OAuth

Pick the ways people can sign in. Olaryn Identity checks it’s really them. Passwords and fingerprints never touch your app.

Passkeys

A fingerprint, face or device PIN. Nothing to remember, nothing to steal.

Learn more

Email links

People type their email, tap the link, and they’re in. No password at all.

Learn more

Google and GitHub

Let people use an account they already have. No new password to make up.

Learn more

Integration workflowassisted setup and approval

Teams can configure a product integration with the documented developer tools, CLI or an AI assistant. Approval remains required.

01

Prepare integration

From your workspace. It has no passwords or secrets in it.

02

Review approval

One click. It lasts 24 hours and you can cancel it any time.

03

Verify sign-in

Check registration, redirects and a completed sign-in flow.

Product-owned sign-in screenidentity handled by the shared service

The sign-in screen lives in your app, with your name, colours and words. Olaryn Identity works behind it, using the same standard as “Sign in with Google”.

Protocol supportOAuth and OpenID Connect

Olaryn Identity speaks OAuth and OpenID Connect, so any library that supports them will work. No special kit to install.

  • Works with common librariesStandard OAuth and OpenID Connect, with PKCE required.
  • Command-line tools tooPeople can sign in to a CLI by approving it on another device.
  • Safe by defaultSigning keys change every 30 days, and sign-ins only return to addresses you registered.