Problem
When configuring openai api, I have multiple api keys for the same base_url because they have different usage scenarios and correspond to different models. However, openwebui does not support me to configure multiple api keys for the same base_url.
Solution
Allows users to configure multiple api keys for the same base_url when configuring an external connection, and supports setting different prefixes for each key as if they were different urls.
Additional context
openwebui works great, thanks to the volunteers.
Originally created by @gaoxiaobei on GitHub (Jan 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8662
**Problem**
When configuring openai api, I have multiple api keys for the same base_url because they have different usage scenarios and correspond to different models. However, openwebui does not support me to configure multiple api keys for the same base_url.
**Solution**
Allows users to configure multiple api keys for the same base_url when configuring an external connection, and supports setting different prefixes for each key as if they were different urls.
**Additional context**
openwebui works great, thanks to the volunteers.
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 @gaoxiaobei on GitHub (Jan 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8662
Problem
When configuring openai api, I have multiple api keys for the same base_url because they have different usage scenarios and correspond to different models. However, openwebui does not support me to configure multiple api keys for the same base_url.
Solution
Allows users to configure multiple api keys for the same base_url when configuring an external connection, and supports setting different prefixes for each key as if they were different urls.
Additional context
openwebui works great, thanks to the volunteers.
@tjbck commented on GitHub (Jan 19, 2025):
Addressed with
71ab8b9c93@gaoxiaobei commented on GitHub (Jan 19, 2025):
Thanks for help!