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

KeyCloak for use with Apicurio #305

Closed
EmanShaaban opened this issue May 5, 2018 · 14 comments
Closed

KeyCloak for use with Apicurio #305

EmanShaaban opened this issue May 5, 2018 · 14 comments

Comments

@EmanShaaban
Copy link

I tried to set Keycloak to be used with Apicurio
I followed the instruction in https://apicurio-studio.readme.io/docs/setting-up-keycloak-for-use-with-apicurio
First I configured KeyCloack with URL ---> http://localhost:8180
screenshot from 2018-05-05 22 23 41
and then configured Apicurio with this settings

when running Apicurio with the command
./bin/standalone.sh -c standalone-apicurio.xml -Djboss.socket.binding.port-offset=100

The Apicurio URL is not working
screenshot from 2018-05-05 22 30 21

@EricWittmann
Copy link
Member

Running Apicurio with that command will start it up running on port 8180, so to access Apicurio you would need to go here:

http://localhost:8180/studio

From there it should redirect you to Keycloak for authentication. Once authenticated you should get redirected back to Apicurio.

At what point in this process are you seeing the failure?

@EricWittmann
Copy link
Member

Do you have Keycloak running on localhost on port 8080?

@EmanShaaban
Copy link
Author

EmanShaaban commented May 6, 2018

I was running Keycloak on different port
I changed keycloack to same ports as Apicurio and now
http://localhost:8180/studio
redirect to
screenshot from 2018-05-06 17 02 16

@EricWittmann
Copy link
Member

OK this indicates that Apicurio is trying to authenticate using a Client ID that has not been added to Keycloak. The actual client-id it's trying to use can be found in the URL, but the window was too small to see it. You could copy/paste that URL here so we can double-check.

Did you import the Realm settings as the instructions indicate? If so, you can log into Keycloak and make sure that there is a apicurio-studio client defined in the apicurio realm.

@EricWittmann
Copy link
Member

Ah ok - so if you don't import the realm file then you won't have any of the appropriate settings in the realm (like the required clients).

Why are you unable to import the realm file? What version of Keycloak are you using?

@eman-shaaban-akad
Copy link

I'm using keycloak-3.4.3.Final, and I downloaded the realm.json file but the file is not imported with Keycloack.

@EricWittmann
Copy link
Member

Did you follow these instructions regarding the realm.json from the article?

After downloading that file, click the Select file button on the Add realm page in Keycloak, then choose the realm.json file you just downloaded. After selecting the realm.json file, you should be able to click the Create button.

If so, was there an error of some sort? I'll try downloading KC again and trying it myself to make sure.

@eman-shaaban-akad
Copy link

yes i follow ale the instructions regarding the realm.json, but I'm unable to import the file.

@EricWittmann
Copy link
Member

EricWittmann commented May 7, 2018

I just tried this - downloaded the latest keycloak and ran through the instructions. The realm.json file import worked just fine. Here is a video of me doing that:

cap

@eman-shaaban-akad
Copy link

I tried to import the realm.json file with the following versions with no success:
keycloak-3.3.0.Final.zip
keycloak-4.0.0.Beta2.zip
keycloak-3.4.3.Final.zip
I guess the issue in the json file.
I searched for a replacement but I id not find

@EricWittmann
Copy link
Member

EricWittmann commented May 9, 2018 via email

@EricWittmann
Copy link
Member

Hi @eman-shaaban-akad - have you given up on this or made any progress? :)

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

No branches or pull requests

3 participants