Apps are the fundamental components of Passage. They provide authentication solutions for an isolated collection of users.

Organizations & Apps

All apps are owned by an Organization. You may have several logically separate apps (e.g. unrelated websites), or, you may use separate Passage apps for different environments (e.g. dev, staging, and production).

App Types

Passkey Complete

Passkey Complete is for those looking to build or replace current authentication systems.

Follow our Quickstart guide to get started with a new passwordless authentication here.

Hosted Login

The Passage hosted login page is an OIDC-compliant identity provider.

Follow our Quickstart guide to get started with a new hosted authentication here.

App Core Settings

All apps require the following settings:



App Name

An app's name distinguishes it from other apps or environments in your Passage Console. A Passage app's name should represent a specific URL and userbase.

Example: "Pet Store"

Example: "Book Store (Production)"

Authentication Origin

An authentication origin is the full URL of the app that Passage will run on. It includes the protocol, domain, and port (if non-standard). Note that Passage biometrics will not work on domains without TLS (i.e. https://), but Passage biometrics will work on http://localhost for testing.

Example: "http://localhost:5000"

Example: ""

*Note: Authentication origins of are not allowed, and will automatically be changed to localhost.

Redirect URL

The redirect URL determines where users will be redirected following successful login. Because Passage stores an authentication token in a cookie, the redirect URL should be on the same domain as the authentication origin. Note that a redirect URL may be set to a relative path.

Example: ""

Example: "/dashboard"

App Transfer

For app organization transfers, please contact our dedicated support team at [email protected]. They will assist you with the necessary steps and provide guidance throughout the process.

Last updated