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
Location of APICURIO_UI_URL when configuring keycloak for Apicurio? #472
Comments
Hoo boy, I do not know how you got into that state. :) As soon as I get a chance, I'll record a quick video of me configuring Keycloak for Apicurio. Maybe that will help. |
What version of Keycloak did you download? |
@EricWittmann the one linked to here: https://apicurio-studio.readme.io/docs/setting-up-keycloak-for-use-with-apicurio I've been tinkering more, no idea why it wasn't shown by default but I managed to add it manually - wasn't too many settings to guess 😄 I'm up and running! Still a question though, should I be using a different keycloak version? |
I used Keycloak version 4.5.0, which is the latest version... |
Glad it's working. Although if the import of Under Client Default Roles for the broker. The 'read-token' role is important. :) |
Oh, and generally speaking newer versions of Keycloak are better. But anything in the 4's should be good. |
Ah that explains why the github link wasn't working :) from the docs it sounded like I must use that version, I recommend revising that! I'll try the latest version as soon as I can. Thanks as always, Eric! |
Hey @tiagosiebler did you ever get this working? |
Ended up using the latest version, I think... nothing needed from your side. Thanks! |
I'm following this and I'm stuck in step 4. I've created a new realm by importing the file. The steps say:
While I'm in the realm, I don't see this in the list of clients:
If I go to the master realm, I do see something for apicurio:
But I don't see anything matching APICURIO_UI_URL or return_url or anything like the screenshots, this is what I see:
What am I missing?
Thanks for the help!
The text was updated successfully, but these errors were encountered: