From tonyj@suse.de Fri Mar 22 19:33:34 2019 From: Tony Jones To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] osc and gnome keyring Date: Fri, 22 Mar 2019 12:33:28 -0700 Message-ID: <645b7165-e6c3-1e5a-318e-cd0bca6e64ae@suse.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8037260536564996658==" --===============8037260536564996658== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Can anyone offer any advice on how to get this to work. In the past it worked= for me but lately I've been unable to get it to work and I've had to resort = to, ahem, clear text passwords. https://en.opensuse.org/openSUSE:OSC "There have been reports that with ... a= dd solely the line gnome_keyring=3D1 instead of keyring=3D1 to the server sec= tion." Is "instead of keyring=3D1" correct or does it mean instead of "use_keyring= =3D1"? Anyways, I've tried every version of use_keyring=3D1, keyring=3D1, gno= me_keyring=3D1, removing python2-keyring and all I get is "Server returned a= n error: HTTP Error 401: Unauthorized" This is using a basic 'osc list' query I have an entry in my gnome keyring for @api.opensuse.org= . It's unfortunate that the debug/verbose options don't provide any info abo= ut the interaction with the keyring as if I remove the opensuse entry from th= e keyring I get the exact same error so it's hard to tell what is occurring. Thanks $ rpm -q openSUSE-release openSUSE-release-20190320-77.1.x86_64 $ osc --version 0.164.2 $ osc -d -v -A https://api.opensuse.org list makeurl: https://api.opensuse.org ['source'] {} GET https://api.opensuse.org/source Server returned an error: HTTP Error 401: Unauthorized Date: Fri, 22 Mar 2019 19:24:40 GMT Server: Apache/2.4.23 (Linux/SUSE) WWW-Authenticate: Basic realm=3D"Use your novell account" Vary: accept-language,accept-charset Strict-Transport-Security: max-age=3D31536000 Upgrade: h2 Connection: Upgrade, close Accept-Ranges: bytes Transfer-Encoding: chunked Content-Type: text/html; charset=3Dutf-8 Content-Language: en Authentication required!

Authentication required!

This server could not verify that you are authorized to access the URL "/source". You either supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.

In case you are allowed to request the document, please check your user-id and password and try again.

If you think this is a server error, please contact the webmaster.

Error 401

api.opensuse.org
Apache/2.4.23 (Linux/SUSE)

To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] Re: osc and gnome keyring Date: Fri, 22 Mar 2019 21:05:17 +0100 Message-ID: <87mulmy8si.fsf@igel.home> In-Reply-To: <645b7165-e6c3-1e5a-318e-cd0bca6e64ae@suse.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5928753068556200966==" --===============5928753068556200966== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On M=C3=A4r 22 2019, Tony Jones wrote: > I have an entry in my gnome keyring for @api.opensuse.o= rg. It's unfortunate that the debug/verbose options don't provide any info a= bout the interaction with the keyring as if I remove the opensuse entry from = the keyring I get the exact same error so it's hard to tell what is occurring. Try starting with the api section in .oscrc removed, then connect to the api and enter the credentials. That should set up the keyring entry for you. Andreas. --=20 Andreas Schwab, schwab(a)linux-m68k.org GPG Key fingerprint =3D 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different." --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============5928753068556200966==-- From tonyj@suse.de Fri Mar 22 20:27:17 2019 From: Tony Jones To: buildservice@lists.opensuse.org Subject: [opensuse-buildservice] Re: osc and gnome keyring Date: Fri, 22 Mar 2019 13:27:15 -0700 Message-ID: <39a9f1b6-3230-c5e3-231a-12dfd4509a36@suse.de> In-Reply-To: <87mulmy8si.fsf@igel.home> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6074135680828666477==" --===============6074135680828666477== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 3/22/19 1:05 PM, Andreas Schwab wrote: > On M=C3=A4r 22 2019, Tony Jones wrote: >=20 >> I have an entry in my gnome keyring for @api.opensuse.= org. It's unfortunate that the debug/verbose options don't provide any info = about the interaction with the keyring as if I remove the opensuse entry from= the keyring I get the exact same error so it's hard to tell what is occurrin= g. >=20 > Try starting with the api section in .oscrc removed, then connect to the > api and enter the credentials. That should set up the keyring entry for > you. Thanks. That fixed it. So I now have use_keyring=3D1 (globally) and a new = api block created by osc that contains keyring=3D1 . --=20 To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org --===============6074135680828666477==--