Passage by 1Password is a passkey authentication solution that provides passwordless login functionality. However, it does not directly integrate with Webflow’s built-in User Accounts system, especially since Webflow does not currently support third-party custom authentication providers for its native authentication flows.
1. Webflow User Accounts Are Not Extensible
- Webflow’s built-in User Accounts feature (available in memberships and logic plans) does not allow custom authentication like OAuth, passkeys, or WebAuthn natively.
- It uses its own system for registration, sign-in, and user management, and cannot be extended to use third-party login systems such as Passage or 1Password.
2. Passage Requires a Custom Backend
- Passage by 1Password requires you to use its JavaScript SDK or API, which must interact with a backend server to handle user sessions and authentication flows.
- Webflow does not allow custom server-side scripting or APIs natively. This means you cannot run the required backend logic within Webflow.
3. Workaround: Use Webflow as a Frontend Only
- You could technically use Passage on a Webflow site if you skip Webflow’s built-in User Accounts and manage authentication via your custom backend.
- This would require using Webflow only to host the frontend, embedding Passage’s authentication UI via custom code, and managing your own user data and gating via custom logic (hosted elsewhere).
4. No Known Native Integration Exists
- As of now, no public use cases or plugins exist that allow direct integration of Passage (or passkeys in general) with Webflow's native User CMS.
- Webflow does not expose its user authentication endpoints or allow overriding them with external identity providers.
Summary
Webflow’s native User Accounts system does not support third-party login solutions like Passage by 1Password. To use Passage, you would need to bypass Webflow User Accounts completely and handle authentication externally via a custom backend.