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

Could someboby tell me how configuring keycloak? #88

Open
sor88 opened this issue Oct 27, 2024 · 1 comment
Open

Could someboby tell me how configuring keycloak? #88

sor88 opened this issue Oct 27, 2024 · 1 comment

Comments

@sor88
Copy link

sor88 commented Oct 27, 2024

I can't configuring huly with keycloak.

@zaroot
Copy link

zaroot commented Nov 6, 2024

I'm running v0.6.333 and this is how I have it setup:

This goes under account service:

 account:
   ...
   environment:
   ...
     - OPENID_CLIENT_ID=${AUTH_CLIENT_ID}
     - OPENID_CLIENT_SECRET=${AUTH_CLIENT_SECRET}
     - OPENID_ISSUER=${AUTH_URL}/realms/${AUTH_REALM}

AUTH_CLIENT_ID should be the "Client ID" you've setup in KeyCloak, in my case "huly-client"
AUTH_CLIENT_SECRET you get from KeyCloak after you create your "Client ID"
I have a custom AUTH_URL and a custom AUTH_REALM but if your spin the keycloak service inside the same docker compose you can use OPENID_ISSUER=https://keycloak/realms/master if you are using the "master" realm and your keycloak service name is "keycloak".

Note that you also have to setup the access urls in KeyCloak > Clients > (your client id, in my case it was "huly-client"
ie: Root URL, Home URL and Valid redirect URIs
In my case the Valid redirect URIs is different since the account service is running on a subdomain (not using the default nginx config provided by huly).

Make sure you check Client authentication > Authentication flow > Standard flow (checkbox)

Hope this helps

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

2 participants