-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
unable to setup Authentication with keycloak #4649
Comments
Did you check Weblate logs? Maybe it's duplicate of #4473? |
Looking at it again, it might just some mess in the cookies as you run both services on localhost domain - they can steal or rewrite cookies from the other app. |
This issue looks like a support question. We try to answer these reasonably fast, but in case you are looking for faster resolution, please consider purchasing support subscription and make Weblate stronger. |
First what is the right value of this env variable please (for Keycloak) ?
|
There is absolutely no log emitted by the weblate container on the sign in process. The only log I can see is on keycloak side and happens right after clicking the "keycloak" button, while the redirection to keycloak's sign in form
EDIT: It seems some logs appear after long waiting time or after sign in through normal form (not keycloak), but not sure if the log are relevant to the keycloak sign in process.
|
This certainly is related, Weblate cannot connect to the keycloak server. Probably the URL should not be localhost unless you are using host networking in the Docker. |
Keycloak run on localhost as well, and on the same network:
|
But it's not localhost for Weblate. Please read on how Docker networking works, for example on https://docs.docker.com/network/network-tutorial-standalone/ |
Ok thank you. |
The issue you have reported seems to be resolved now.
|
Hey I am also experiecing issues with keycloak installation, did you use this in the end? :
Have you tried to use OIDC plugin instead of the oauth2 one? |
Describe the bug
Hi,
With my team we are trying to setup our weblate docker container to use Keycloak as authentication system.
We followed the only documentation that exists on this subject -> https://docs.weblate.org/en/weblate-4.2.2/admin/install/docker.html?#keycloak
So far we have, in a local environment, weblate running and working.
Here is the
docker-compose
, relevant part:For keycloak side, we followed the steps described in the comment on the source file -> https://github.com/python-social-auth/social-core/blob/master/social_core/backends/keycloak.py
On the sign in form of weblate, now we have a button "keycloak". If we click on it, we are redirected to keycloak's own sign in form:
Here if we try to connect with wrong credential, keyclaok informs us about that, and we have to retry, but if we enter good one, we are redirected back to weblate -> http://localhost:8090/accounts/login/.
And here the problem happens: An error message appears in the UI
And we are not authenticated. There is no error in keycloak logs and in weblate logs.
Due to lack of proper documentation/guide and no explicit log, we cannot figure out what the problem is.
The text was updated successfully, but these errors were encountered: