Clarification on how to configure Registry with Keycloak using authorization.

[carlesarnal]

Unfortunately, I don't understand how I can assotiate user with Apicurio roles. After load apicurio-realm.json from github I see roles registry-admin and registry-user in registry-api client. Also I see Realm Roles sr-admin, sr-developer and sr-readonly. If I create group and assign it to registry-admin (or sr-admin) after login I redirect on page /explore with error "Error searching for artifacts." and 403 response in log.

Originally posted by @SamMc75 in #5327 (reply in thread)

[carlesarnal]

Hi @SamMc75, I recommend checking https://www.apicur.io/registry/docs/apicurio-registry/3.0.x/getting-started/assembly-configuring-registry-security.html instead of copying a realm from the repo.

If you want more concrete examples, we have some in our integration-tests (not the best place).

Registry-in-memory: https://github.com/Apicurio/apicurio-registry/blob/main/integration-tests/src/test/resources/infra/in-memory/registry-in-memory-secured.yml

Keycloak with realm: https://github.com/Apicurio/apicurio-registry/blob/main/integration-tests/src/test/resources/infra/auth/keycloak.yml