Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration with Keycloak #1353

Closed
amalkurup89 opened this issue Mar 17, 2021 · 11 comments
Closed

Integration with Keycloak #1353

amalkurup89 opened this issue Mar 17, 2021 · 11 comments
Labels
Question Further information is requested

Comments

@amalkurup89
Copy link

Is Apicurio registry integrated with Keycloak

@jsenko
Copy link
Member

jsenko commented Mar 17, 2021

Yes, but it's disabled by default, see https://github.com/Apicurio/apicurio-registry/blob/master/app/src/main/resources/application.properties#L105
Could you provide more details about your issue?
CC @carlesarnal

@amalkurup89
Copy link
Author

@jsenko Just like apicurio studio, I need a login functionality in Apicurio registry and logged in user should be entitled to view artifacts uploaded or shared with him, on registry UI

@carlesarnal
Copy link
Member

hi @amalkurup89, you'll need to provide your own Keycloak server with a Realm properly configured with users matching the roles defined in the application.properties that Jakub shared with you. Let me know if you need help.

@amalkurup89
Copy link
Author

amalkurup89 commented Mar 17, 2021

@jsenko @carlesarnal I have setup the below environment variables, but still UI authentication is not enabled

  • name: AUTH_ENABLED
    value: 'true'
  • name: KEYCLOAK_URL
    value: 'keycloakurl/auth'
  • name: KEYCLOAK_REALM
    value: realmname
  • name: KEYCLOAK_API_CLIENT_ID
    value: clientid
  • name: KEYCLOAK_UI_CLIENT_ID
    value: clientid

@carlesarnal
Copy link
Member

Hi @amalkurup89, here's a realm for you to import into Keycloak.

The appropriate values for that realm are:

  • name: AUTH_ENABLED
    value: 'true'
  • name: KEYCLOAK_URL
    value: {KEYCLOAK_SERVER_URL}/auth
  • name: KEYCLOAK_REALM
    value: registry
  • name: KEYCLOAK_API_CLIENT_ID
    value: registry-api
  • name: KEYCLOAK_UI_CLIENT_ID
    value: registry-ui

Let me know if you need anything else.

@EricWittmann
Copy link
Member

@amalkurup89 What version of Apicurio Registry are you using? Authentication via KC is new to version 2.0.x, which is just in the process of being released this month.

You would need to use e.g. 2.0.0.RC1 for this to work.

@EricWittmann EricWittmann added the Question Further information is requested label Mar 29, 2021
@tillias
Copy link

tillias commented Mar 29, 2021

Is there any ticket to subscribe to or is it part of "Apicurio Registry 2.0.x" version? We would be also very interested in this feature

@EricWittmann
Copy link
Member

Auth via Keycloak is part of the 2.0.x release.

@carlesarnal
Copy link
Member

Closing this, if anyone has any objections, please reopen.

@arthurguau
Copy link

Docker-compose and Quarkus based installation

It says "This setup contains a fully configured Apicurio Registry package already integrated with Keycloak. ", but I still can not get it keycload enabled after strictly followed steps specified in Docker-compose and Quarkus based installation. Not sure if I have missed some steps?

@carlesarnal
Copy link
Member

Hi @arthurguau, could you please raise a new issue since yours is not strictly related to this one? Also please include any stacktrace and anything you think may be relevant, thanks!.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Further information is requested
Projects
None yet
Development

No branches or pull requests

6 participants