search

Apicurio / apicurio-registry

An API/Schema registry - stores APIs and Schemas.
https://www.apicur.io/registry/
Apache License 2.0
609 stars 269 forks source link

Apicurio ui - use without authorization & authentication #5175

Open Sonique opened 2 months ago

Sonique commented 2 months ago

Feature or Problem Description

cannot run ui without keycloak

Proposed Solution

disable authorization

apicurio-bot[bot] commented 2 months ago

Thank you for reporting an issue!

Pinging @EricWittmann to respond or triage.

EricWittmann commented 2 months ago

What do you mean by disable authorization? It's already possible to disable authentication + authorization in both the backend and frontend. That works just fine - we use that mode for internal testing all the time.

Is there something else/different you are looking for?

Note: disabling authentication entirely is obviously not recommended for a production system.

Sonique commented 2 months ago

It's already possible to disable authentication + authorization in both the backend and frontend. That works just fine - we use that mode for internal testing all the time.

Is there something else/different you are looking for?

Note: disabling authentication entirely is obviously not recommended for a production system.

Sorry, maybe I cannot found in documentation, so I disable in swagger registry and it automatically disables authorization on the front end? How to disable authorization?

carlesarnal commented 2 months ago

Both are disabled by default, unless you explicitly enable them. Here's the documentation you're looking for. Let me know if there's anything unclear there.

EricWittmann commented 1 month ago

One more thing to note. In the latest version the UI and API components are separated into separate docker images. In this new configuration the authentication and authorization settings are fetched by the UI from the API component.

What this means is that all configuration is done on the API container. We will have updated documentation for this shortly.

This is in contrast to what we do in 2.6.x. in that version there is only one container image. And so of course configuration happens all on that one container image.