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

Feat: Guest Mode #3058

Open
MarlNox opened this issue Jun 12, 2024 · 1 comment
Open

Feat: Guest Mode #3058

MarlNox opened this issue Jun 12, 2024 · 1 comment

Comments

@MarlNox
Copy link

MarlNox commented Jun 12, 2024

Problem:
When users are not logged in, there's currently no option for them to engage in conversations through the chat in the open web UI without their interactions being put in history, like in the Single User mode where all history is still recorded so it can't be used simultaneously by many users.

Solution:
Introduce a "Guest Mode" within the open web UI, where users can access chat functionality without the need to create personal accounts. Upon choosing the "No Login" option, users are automatically provided with predefined login credentials (e.g., username and password) generated by the system. In this Guest Mode, the sidebar displaying chat history is hidden, ensuring that no conversation records are stored. The guest mode should be in addition to the multi-user sign in rather than an either-or scenario.
Alternatives:
Consider allowing users to access limited chat functionality without logging in, with the option to create an account for accessing more features and retaining chat history.

@MarlNox
Copy link
Author

MarlNox commented Jun 13, 2024

FIX i implemented locally - potentially useful input for the maintainers/devs of OpenWebui:

  1. Create an iframe html in static folder, and connect it with the src/routes/auth/ page.svelte, as well as setting the safe origin for requests.
  2. Create a Guest user with some credentials whatever ([email protected], root password)
  3. Create a redirect button with JS to do the following: authenticate the user with the hardcoded sigin details.
  4. Fetch Token, insert it via iframe into the origin of the openwebui (cross-origin set LocalStorage token key)
  5. if logged in user is Guest, then hide the content of the sidebar. As well as other buttons which give access to chat history, or account settings.

Additional stuff:
a) create a new chat before redirecting to that specific chat.

TO DO from my side:

a) Generate the response to that new chat's query using the selected Pipeline.

 - From what im seeing there's no API endpoint for generation given a modelname, chatid, and userid. 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant