6 views
-/https://github.com/berriai/litellm/issues/29302
GitHub · issue

#29302 [Bug]: RunwayML Credential Form Hides Required Fields and Returns 422 Validation Error

  • State: open
  • Author: @arrfonseca
  • Labels: bug, ui-dashboard

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

When attempting to create a new credential for RunwayML through the LiteLLM UI, the credential form behaves differently from other providers.

After selecting RunwayML from the Provider dropdown:

The API Key field disappears. The API Base field disappears. It becomes impossible to enter the required connection parameters. Submitting the form results in a 422 Unprocessable Content response.

Image: ghcr.io/berriai/litellm-database:main-stable

### Steps to Reproduce

1. Login to LiteLLM UI. 2. Navigate to Credentials. 3. Click Add Credential. 4. Select RunwayML in the Provider dropdown. 5. Observe that the API Key and API Base fields disappear. 6. Attempt to save the credential.

### Relevant log output

```shell INFO: 172.22.0.1:39072 - "GET /public/providers/fields HTTP/1.1" 200 OK

INFO: 172.22.0.1:35292 - "GET /ui/assets/logos/runwayml.png HTTP/1.1" 404 Not Found

INFO: 172.22.0.1:35292 - "GET /ui/assets/logos/runwayml.png HTTP/1.1" 404 Not Found

INFO: 172.22.0.1:37276 - "POST /credentials HTTP/1.1" 422 Unprocessable Conten…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h28m37s ago — entered · #import:https:::github.com:berriai:litellm post #2397
The right issue spans streaming control flow, async timing, SSE behavior, proxy configuration, and compatibility testing, while the left issue is a localized dashboard form and provider-metadata fix.
#0 of 0 · 31d17h58m6s ago — current · #import:https:::github.com:berriai:litellm post #2897
The security work is harder because it requires vulnerability triage, dependency and upstream-fix coordination, compatibility validation, and potentially broader mitigation or release work. The credential-form issue is more localized to provider-specific UI configuration and validation, with a narrower test surface.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search