Originally created by @tkg61 on GitHub (Aug 28, 2024).
Is your feature request related to a problem? Please describe.
We would like to enable this to just be a chat client and not have users use it for API based interaction.
Describe the solution you'd like
Would like to have a flag to disable the API key generation for users and to disable the endpoint for security purposes.
Describe alternatives you've considered
if we could have #4477 implemented and allow the openwebui api key to essentially forward the request to the backend server using a users unique openai api key we would be happy to keep the API key on but we are trying to limit API based operations to unique keys and just chat to a single openai key. Hope that makes sense
Thought about blocking routes via nginx but that might get finicky
Additional context
Originally created by @tkg61 on GitHub (Aug 28, 2024).
**Is your feature request related to a problem? Please describe.**
We would like to enable this to just be a chat client and not have users use it for API based interaction.
**Describe the solution you'd like**
Would like to have a flag to disable the API key generation for users and to disable the endpoint for security purposes.
**Describe alternatives you've considered**
if we could have #4477 implemented and allow the openwebui api key to essentially forward the request to the backend server using a users unique openai api key we would be happy to keep the API key on but we are trying to limit API based operations to unique keys and just chat to a single openai key. Hope that makes sense
Thought about blocking routes via nginx but that might get finicky
**Additional context**
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tkg61 on GitHub (Aug 28, 2024).
Is your feature request related to a problem? Please describe.
We would like to enable this to just be a chat client and not have users use it for API based interaction.
Describe the solution you'd like
Would like to have a flag to disable the API key generation for users and to disable the endpoint for security purposes.
Describe alternatives you've considered
if we could have #4477 implemented and allow the openwebui api key to essentially forward the request to the backend server using a users unique openai api key we would be happy to keep the API key on but we are trying to limit API based operations to unique keys and just chat to a single openai key. Hope that makes sense
Thought about blocking routes via nginx but that might get finicky
Additional context