FlowiseAI/Flowise

[FEATURE] Allow User Authentication for embed front-end, as well as main conversation and prompt question history

Open

#3.655 geöffnet am 9. Dez. 2024

Auf GitHub ansehen
 (2 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)TypeScript (52.823 Stars) (24.335 Forks)batch import
enhancementhelp wanted

Beschreibung

Describe the feature you'd like Currently, when using embed code in own project, it is working but i want to show prompt screen after authenticating user.

Without User Login: System work same as it is, it is fine but here chat conversion history should not maintain. browser reload prompt must be disappear.

With User Login: Chat conversation history maintain and this history save based on logged in user. If user login anywhere history of that specific user should be show.

Prompt Question History: Login User Prompt Question should maintain as history in left side panel.

Additional context

Screenshot from 2024-12-09 11-05-56

Contributor Guide

Tech Stack
typescriptreactnodejspostgresql
Domain
authenticationfull stackfrontendbackend
Issue Type
feature
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
4
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
3-5 days
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
fresh
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
needs investigation
Voraussetzungen
Understanding of authentication flowsFamiliarity with React and Node.jsKnowledge of database schema design
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
30
Research-Richtung
Investigate the current embed front end implementation in Flowise (likely in packages/components) and the existing authentication system (if any). Look at how conversation history is currently stored (database schema in packages/server or database). Review the user model and any existing auth middleware. The requested feature requires adding user login to the embed, persisting chat history per user, and showing prompt question history. Check if there are any existing API endpoints for user management. The issue does not specify backend technology, but Flowise uses Prisma ORM and SQLite/PostgreSQL based on its open source code.