Can't log in any more to Bugzilla
I last successfully logged in to https://bugzilla.opensuse.org/ on 2021-03-16. Today 04-20, I could not authenticate. It looks like there is a new authentication infrastructure (whose name I didn't copy down). I went through the "reset password" procedure twice, and finally got on once, but once again I'm unable to get on. The login page shows an error message, "Bugzilla requires a valid user name and password". This month I've installed a password manager, Bitwarden. When appropriately clicked on, it will insert the user ID and password in the login form, which it "successfully" did with all three passwords (original and two new ones). But whatever it inserted, was not acceptable to the auth system. For the new passwords I generated new 16 byte random ones, and saved them in a file, and pasted them onto the password change form, and then the Bugzilla login form (after Bitwarden's rendition was rejected). These also were rejected. The one time I got on, I was very low tech: I typed everything letter by letter. But 3 hours later I could not repeat that performance (with the same password, the second new one). (I tried several times.) So I signed up with the mailing list system, which uses a different infrastructure including a choice of Identity Providers; I used the OpenSuSE one. Actually I gave it my latest Bugzilla credentials, but it wanted to sign me up with a new identity. Apparently the Bugzilla provider shares identity info with it; it knew my e-mail address without being told, but it did not re-use my user ID, which combines my normal loginID and my work site name, so is very likely to be unique. Does anyone have any idea what's going on, and how I can authenticate to Bugzilla? I'm thinking that the login form has been updated with Javascript provided by the new outsourced Identity Provider, that can distinguish keystroke input from program-generated text and which rejects the latter as a defense against bots. While bot defense is not bad, you get a whole lot better defense if you encourage the users to use a password manager with long random passwords. -- James F. Carter Email: jimc@jfcarter.net Web: http://www.math.ucla.edu/~jimc (q.v. for PGP key)
jimc wrote:
I last successfully logged in to https://bugzilla.opensuse.org/ on 2021-03-16. Today 04-20, I could not authenticate. It looks like there is a new authentication infrastructure (whose name I didn't copy down).
AFAIK, nothing has changed in that regard - but just in case, I've just logged out and in again, looks exactly the same. -- Per Jessen, Zürich (8.2°C) Member, openSUSE Heroes.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2021-04-21 at 08:55 +0200, Per Jessen wrote:
jimc wrote:
I last successfully logged in to https://bugzilla.opensuse.org/ on 2021-03-16. Today 04-20, I could not authenticate. It looks like there is a new authentication infrastructure (whose name I didn't copy down).
AFAIK, nothing has changed in that regard - but just in case, I've just logged out and in again, looks exactly the same.
I tried to login into bugzilla (using a bug report): +++··················· Bugzilla – Bug 1183990 I think I found the cause of a kernel lock when attempting hibernation Last modified: 2021-03-30 12:31:33 UTC Home New Browse Search [ ] [?] Reports Requests Help [ ] [ ] LOGIN [x]⁽¹⁾ Forgot Password First Last Prev Next This bug is not in your last search results. ···················++- (it is not clear what the 'x' in (1) above is for) using KeepPassXC autotype feature, it did not work. And KeepPassXC "types" slowly. I got another page with information: +++··················· Bugzilla needs a legitimate login and password to continue. Login [ ] password [ ] [/] Restrict this session to this IP address (using this option improves security) (Note: you should make sure cookies are enabled for this site. Otherwise, you will be required to log in frequently.) ···················++- Ant this time autotype worked. It is exactly the same password, obviously. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYH/8NRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVZpYAnR4DCEFprkakKPUcAeu+ PPfWTOBEAJsEkUpcBKvrjtn6NnwwmXjTsn/fNw== =R5Is -----END PGP SIGNATURE-----
participants (3)
-
Carlos E. R.
-
jimc
-
Per Jessen