Comment on page
Apps
Apps are the fundamental components of Passage. They provide authentication solutions for an isolated collection of users.
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).
Passkey Complete is for those looking to build or replace current authentication systems.
Passkey Flex adds passkeys to existing authentication systems.
Coming soon
All apps require the following settings:
Field | Description |
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: "https://www.example.com" *Note: Authentication origins of 127.0.0.1 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: "https://www.example.com/dashboard" Example: "/dashboard" |
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.