As far as I know, it's either username/password OR SSH key (with sshd if it's a key with a password, else without) for pushing to a repo on gitlab.
Maren Am 22.09.2018 um 21:57 schrieb POPOV, Anastas (Devnya) BGR: > Hello, > > Thank you for your reply! > > I already had set up the Weblate configuration to use GitLab OAuth2. > But the more I read the more I think that this configuration is used only for > users login and not for GitLab repository authentication - could you confirm > that? > > With above mentioned configuration Weblate still asks for username/password > for GitLab in the console when I create a component instead of directly > cloning the repository. > > Best regards, > > -----Original Message----- > From: Weblate > [mailto:[email protected]] On Behalf Of > Michal Cihar > Sent: Saturday, September 22, 2018 6:40 PM > To: [email protected] > Subject: Re: [Weblate] Access https gitlab repository with invalid certificate > > 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://secure-web.cisco.com/1ZzWpfsu9Q4NtzbOyvqlvrKRUe7TokNOBZ-W0wjdpF8XPsSHMk_4RyOXMAP2Ivs-fLDXQsKyqoADrc0LAIzvS1ilwbc1L1ucLtpGa1lJujqChXY2TZrOiZ5gngZmaOkeoTpbNdczGwsvZsqr2cS7fqlojJN-E592edgz6DK9Ik0x3SuRnyOUPHns_EBcZ1b8I_IQyWlzeQuTeO7FXJPyNW3F2lhxCeaUHGxDb2UV9rerb5TJgVIOALiGePC-WFNxo1yNNXENdsPnvUQ-U8KPStGEWYD9m16w6GbCzw_PiF3zdlVZs2kK_EHmgpaslLN6Z4iDhuHEjL2_WZfRJEjrqOw/https%3A%2F%2Fdocs.weblate.org%2Fen%2Flatest%2Fadmin%2Fauth.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://secure-web.cisco.com/1lmnEOcQ-J5e50UMT8Q4geY8y6EwblcbXUUuJSe_JEoEUyf1XD6JmbhwTv-szb3Yyrf2LWUmrbhKpjI78Q_5jZdWyFqcNOYrP-Ca1czjnHNI8OzQ6DgpOxYGo6f1eGvXDTKR2FJKOsRDnjpmbkeFgZ6akf0-ayBx4usO1OoCVVGWCiYOjrWuVzBY5wkYpXduhkm-6eLRo2IHH9rti_fsyohqXYS2fwaSVMYKedr6oxU1RiwUS4p8ZNMh_wKseTwC5SDpDh1bOqhus04xKczWteQy92WeajltTfzYl97lDc7oHPceCdyXaEuTKDLCk-QOYEUYYxMsehSO32XUq39YwPw/https%3A%2F%2Fcihar.com%2F > | > https://secure-web.cisco.com/1iX0iUCrFyBitipHEpEcSIQwvY1ELPrGovECitnTSLWGmb6iLIHtMFAnO0e3T9rFkr_Uaz4R4_RxMAvpTTh0qzPLwdqvFy1_mINL-U53ajRBOczHcSJQReMUgE5XXIO7kSFZ7zIxraClZbM5yC5Ytwq1ltwE3xQxtCVMzvcaLlqPpE-K2C9U8GlzUqm0ugONt-L0mTefu1lucn33zF5BIzaEmuyKymu9unD9XNtjCHVKMqZNw_EEOI3PkbaKJ6u8P6mcil94awkVNQn9gySauOcL1OWoBb-ZE7yQSoFLZ7mNSRvfXmpAtTKxwZ5MZYWnUfDLJBT2s-9k350ACeR-4zg/https%3A%2F%2Fweblate.org%2F > > Политика за защита на личните данни / GDPR > Policy<https://www.devnyacement.bg/bg/personal_data> > _______________________________________________ > Weblate mailing list > [email protected] > https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate > _______________________________________________ Weblate mailing list [email protected] https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
