Please select the area the issue is related to
AI Workspace
Please select the aspect the issue is related to
Aspect/UX (User experience, flows, usability, clarity), Aspect/Configuration (Config files, settings, env vars, defaults)
Description
When a user with the default Consumer role creates a Gen AI application from the AI Workspace and tries to add an LLM proxy to it, the available proxies are listed, but the API keys associated with the selected proxy are not displayed. Since users with this role cannot generate their own API keys, they are left in a blocked state and cannot proceed with configuring the LLM proxy.
Steps to Reproduce
- Create an LLM provider as a Developer user.
- Create an LLM proxy by connecting it to the LLM provider as a Developer user.
- Log in to the AI Workspace as a user with the Consumer role.
- Create a Gen AI application.
- Try to add an LLM proxy to the Gen AI application.
- Observe that the API key list is empty.
Severity Level of the Issue
Severity/Critical (Core functionality is broken but there is a workaround. Need urgent attention)
Environment Details (with versions)
1.0.0
Please select the area the issue is related to
AI Workspace
Please select the aspect the issue is related to
Aspect/UX (User experience, flows, usability, clarity), Aspect/Configuration (Config files, settings, env vars, defaults)
Description
When a user with the default Consumer role creates a Gen AI application from the AI Workspace and tries to add an LLM proxy to it, the available proxies are listed, but the API keys associated with the selected proxy are not displayed. Since users with this role cannot generate their own API keys, they are left in a blocked state and cannot proceed with configuring the LLM proxy.
Steps to Reproduce
Severity Level of the Issue
Severity/Critical (Core functionality is broken but there is a workaround. Need urgent attention)
Environment Details (with versions)
1.0.0