Skip to content

Create provider profile: a profile with credentials and endpoints is always refused (no L7 or allow_uninspected_credentials option) #148

Open

Description

@Gkrumbach07

What happens

You can't create a provider profile with a credential and a network endpoint from the Create provider profile form. The gateway refuses it:

endpoints[0].allow_uninspected_credentials: credentialed endpoint 'api.example.com:443' uses L4-only; configure L7 inspection or explicitly set allow_uninspected_credentials: true

The gateway is enforcing a real rule here. A credentialed endpoint has to use L7 inspection or opt out with allow_uninspected_credentials: true. The form can't do either one: each endpoint row has only a host and a port (CreateProfileModal.tsx, type ProfileEndpoint in frontend/src/types/index.ts). So the form can only create profiles that have no credentials or no endpoints.

Steps to reproduce

  1. Open Provider profiles → Create profile.
  2. Add a credential (say api_key → CUSTOMER_API_KEY, Required).
  3. Add an endpoint (api.example.com, 443).
  4. Click Create profile. The validation error above appears.

Workaround

Use Import from files. The profile file parser (frontend/src/utils/profileFile.ts) accepts allow_uninspected_credentials and the L7 fields:

endpoints:
  - host: api.example.com
    port: 443
    allow_uninspected_credentials: true

Expected

The endpoint rows let you configure L7 inspection (protocol / access preset / TLS, plus binaries) or tick Allow uninspected credentials. The checkbox should come with a warning that the credential can't be inspected. AddEndpointModal in the policy rule editor already has that checkbox, so it can be reused. The form should also warn before submitting when a credentialed endpoint has neither.

Also seen in the same form

  • Layout overlap: the "Add credential" link and the "Credential schema: what secrets providers of this type need" helper text render on top of the "Network endpoints" label.
  • No host check: a host with a trailing slash (api.example.com/) is accepted and sent to the gateway as is.

Also noted in the 2026-11 UX sweep of the creation flows ("the Create profile form can't make a credentialed profile").

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions