Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Documentation] AAD, i know how to configure Quivr auth methods #1580

Closed
2 tasks
mamadoudicko opened this issue Nov 3, 2023 · 2 comments
Closed
2 tasks
Assignees
Labels
area: docs Related to documentation or under the /docs directory

Comments

@mamadoudicko
Copy link
Contributor

mamadoudicko commented Nov 3, 2023

Validation:

  • Go to Quivr Doc
  • Check that Authentification modes are explain in dev section
@mamadoudicko mamadoudicko self-assigned this Nov 3, 2023
@mamadoudicko mamadoudicko converted this from a draft issue Nov 3, 2023
Copy link

dosubot bot commented Nov 3, 2023

🤖

Hello @mamadoudicko,

Great to see you again! I hope you're doing well. I've seen your issue and I'm currently looking into it. I'll ensure to provide a comprehensive solution as soon as possible. Hang tight!

@dosubot dosubot bot added the area: docs Related to documentation or under the /docs directory label Nov 3, 2023
Copy link

dosubot bot commented Nov 3, 2023

🤖

Based on the information available in the Quivr repository, the application currently supports three authentication methods: Password-based authentication, Google Login, and Magic Link (Email-based authentication). This is inferred from the keys present in the JSON file at frontend/public/locales/en/login.json.

However, the specific steps to configure each of these authentication methods are not explicitly documented in the repository. It's possible that this information might be available in the application's internal documentation or setup guides, or it might be a part of the application's setup process.

As for the implementation of these authentication methods, they are handled in the backend/auth/auth_bearer.py file. This file contains the AuthBearer class, which includes methods for checking the scheme of the credentials, authenticating the user, and getting a test user. The get_current_user function, which returns the current user, is also defined in this file. The authentication process involves verifying the token or API key and decoding the access token or getting the user from the API key. You can review the code in backend/auth/init.py and backend/auth/auth_bearer.py for more details.

If you need more specific information or guidance on configuring these authentication methods, could you please provide more details about the issues you're facing or the information you're looking for? This will help me provide a more accurate and helpful response.

Sources


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@mamadoudicko mamadoudicko moved this from Todo to In Progress in Quivr's Roadmap Nov 6, 2023
StanGirard pushed a commit that referenced this issue Nov 6, 2023
@mamadoudicko mamadoudicko moved this from In Progress to To Be Validated in Quivr's Roadmap Nov 6, 2023
@Chloeroumengas Chloeroumengas moved this from To Be Validated to Done in Quivr's Roadmap Nov 7, 2023
coolCatalyst added a commit to coolCatalyst/quivr that referenced this issue Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Related to documentation or under the /docs directory
Projects
None yet
Development

No branches or pull requests

2 participants