mirror of
https://github.com/QuivrHQ/quivr.git
synced 2024-12-15 09:32:22 +03:00
d54f370ed4
# Description Please include a summary of the changes and the related issue. Please also include relevant motivation and context. ## Checklist before requesting a review Please delete options that are not relevant. - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented hard-to-understand areas - [ ] I have ideally added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged ## Screenshots (if appropriate):
25 lines
880 B
Plaintext
25 lines
880 B
Plaintext
---
|
|
title: Authentication Method
|
|
description: Learn how to configure authentication in Quivr.
|
|
---
|
|
|
|
|
|
# Authentication Methods
|
|
|
|
Quivr offers three authentication methods when self-hosting. You can choose which authentication methods you want to offer to your users from these three options:
|
|
|
|
1. **Email/Password Authentication**
|
|
2. **Google Authentication**
|
|
3. **Magic Link Authentication**
|
|
|
|
To enable one or more of these methods, you need to configure the following environment variables in your `.env` file:
|
|
|
|
```bash
|
|
# Authentication Configuration
|
|
NEXT_PUBLIC_AUTH_MODES=magic_link,google_sso,password
|
|
```
|
|
Since each of these methods uses Supabase, you should configure your Supabase instance to support the chosen methods.
|
|
|
|
Please refer to the [Supabase documentation](https://supabase.com/docs/guides/auth) for more information on how to configure each authentication method.
|
|
|