Hello On Tue, 2018-09-18 at 22:05 +0000, POPOV, Anastas (Devnya) BGR wrote: > Thanks a lot! That did the trick! I searched the entire documentation > but didn't find how to overcome this specific case.
The documentation won't contain suggestions how to make system less secure... > But now when I try to create a component in Weblate, the server > hangs. If I check the server console - I see that git waits for > username/password in the server console. > > I want to use GitLab OAuth Authentication with gitlab application > providing application id and application secret. For that I generated > new application in our self-hosted GitLab server and then configured > in $BASE_DIR/weblate/settings.py the following lines: > > SOCIAL_AUTH_GITLAB_KEY = '<application id generated by GitLab' > SOCIAL_AUTH_GITLAB_SECRET = '<secret generated by GitLab>' > SOCIAL_AUTH_GITLAB_SCOPE = ['api'] > > Do I need anything else additionally on Weblate side in order to > work? I thought using Application in GiLab was enough. Or is that the > GitLab OAuth Weblate Authentication works only with GitLab in the > clound and not self-hosted? You need to add GitLab authentication backend and configure your GitLab URL, see the docs: https://docs.weblate.org/en/latest/admin/auth.html#gitlab-oauth2 However you will probably have to deal with untrusted cert there as well, I'm not really sure how to do that easily. -- Michal Čihař | https://cihar.com/ | https://weblate.org/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Weblate mailing list [email protected] https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
